aboutsummaryrefslogtreecommitdiffstats
path: root/install
diff options
context:
space:
mode:
authorfriendica <info@friendica.com>2015-02-26 16:41:38 -0800
committerfriendica <info@friendica.com>2015-02-26 16:41:38 -0800
commitdce0bb0ef806d88a855c362f359b7b1a350deff2 (patch)
treef2ad96b9a75d9ac23f48ec611cb2bd3587990561 /install
parentb79d2420520d72b878982f3b98052c0f816af83e (diff)
downloadvolse-hubzilla-dce0bb0ef806d88a855c362f359b7b1a350deff2.tar.gz
volse-hubzilla-dce0bb0ef806d88a855c362f359b7b1a350deff2.tar.bz2
volse-hubzilla-dce0bb0ef806d88a855c362f359b7b1a350deff2.zip
finish converting "delete" to trash icons for consistency. The 'x' was left in a couple of places like the group list widget and saved search term widget and ignoring friend suggestions where it was more appropriate to leave it.
Diffstat (limited to 'install')
-rw-r--r--install/update.php8
1 files changed, 6 insertions, 2 deletions
diff --git a/install/update.php b/install/update.php
index ee13bee78..70ffb1ebf 100644
--- a/install/update.php
+++ b/install/update.php
@@ -26,10 +26,14 @@ define( 'UPDATE_VERSION' , 1138 );
* The DB_UPDATE_VERSION will always be one greater than the last numbered script in this file.
*
* If you change the database schema, the following are required:
- * 1. Update the file database.sql to match the new schema.
+ * 1. Update the files schema_mysql.sql and schema_postgres.sql to match the new schema.
+ * Be sure to read doc/sql_conventions.bb ($yoururl/help/sql_conventions) use only standard
+ * SQL data types where possible to keep differences in the files to a minimum
* 2. Update this file by adding a new function at the end with the number of the current DB_UPDATE_VERSION.
* This function should modify the current database schema and perform any other steps necessary
- * to ensure that upgrade is silent and free from requiring interaction.
+ * to ensure that upgrade is silent and free from requiring interaction. Review to ensure that it
+ * will run correctly on both postgres and MySQL/Mariadb. It is very difficult and messy to fix DB update
+ * errors. Once pushed, it requires a new update which undoes any damage and performs the corrected updated.
* 3. Increment the DB_UPDATE_VERSION in boot.php *AND* the UPDATE_VERSION in this file to match it
* 4. TEST the upgrade prior to checkin and filing a pull request.
*