From 32e96d2647b4f535bf329caf160336f3358ce423 Mon Sep 17 00:00:00 2001 From: Friendika Date: Wed, 9 Mar 2011 02:12:32 -0800 Subject: reload plugins if they change --- update.php | 3 +++ 1 file changed, 3 insertions(+) (limited to 'update.php') diff --git a/update.php b/update.php index 131014d4a..422c27c7b 100644 --- a/update.php +++ b/update.php @@ -374,3 +374,6 @@ function update_1038() { q("ALTER TABLE `item` ADD `plink` CHAR( 255 ) NOT NULL AFTER `target` "); } +function update_1039() { + q("ALTER TABLE `addon` ADD `timestamp` BIGINT NOT NULL DEFAULT '0'"); +} \ No newline at end of file -- cgit v1.2.3 From 7250b04dbdbc10a6470d34ffa6dacc97d43cd347 Mon Sep 17 00:00:00 2001 From: Friendika Date: Wed, 9 Mar 2011 02:17:08 -0800 Subject: EOF --- update.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'update.php') diff --git a/update.php b/update.php index 422c27c7b..88d038f94 100644 --- a/update.php +++ b/update.php @@ -376,4 +376,4 @@ function update_1038() { function update_1039() { q("ALTER TABLE `addon` ADD `timestamp` BIGINT NOT NULL DEFAULT '0'"); -} \ No newline at end of file +} -- cgit v1.2.3 From 7b9dff1db7a1a03e237103ff28a4ec32d40af959 Mon Sep 17 00:00:00 2001 From: Friendika Date: Wed, 9 Mar 2011 16:57:22 -0800 Subject: automated versioning --- update.php | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'update.php') diff --git a/update.php b/update.php index 88d038f94..fe8052b00 100644 --- a/update.php +++ b/update.php @@ -11,24 +11,24 @@ * Each function in this file is named update_nnnn() where nnnn is an increasing number * which began counting at 1000. * - * At the top of the file "boot.php" is a define for BUILD_ID. Any time there is a change + * At the top of the file "boot.php" is a define for DB_UPDATE_VERSION. Any time there is a change * to the database schema or one which requires an upgrade path from the existing application, - * the BUILD_ID is incremented. + * the DB_UPDATE_VERSION is incremented. * - * The current BUILD_ID is stored in the config area of the database. If the application starts up - * and BUILD_ID is greater than the last stored build number, we will process every update function - * in order from the currently stored value to the new BUILD_ID. This is expected to bring the system + * The current DB_UPDATE_VERSION is stored in the config area of the database. If the application starts up + * and DB_UPDATE_VERSION is greater than the last stored build number, we will process every update function + * in order from the currently stored value to the new DB_UPDATE_VERSION. This is expected to bring the system * up to current without requiring re-installation or manual intervention. * - * Once the upgrade functions have completed, the current BUILD_ID is stored as the current value. - * The BUILD_ID will always be one greater than the last numbered script in this file. + * Once the upgrade functions have completed, the current DB_UPDATE_VERSION is stored as the current value. + * 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. - * 2. Update this file by adding a new function at the end with the number of the current BUILD_ID. + * 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. - * 3. Increment the BUILD_ID in boot.php + * 3. Increment the DB_UPDATE_VERSION in boot.php * 4. TEST the upgrade prior to checkin and filing a pull request. * */ -- cgit v1.2.3