streams/Zotlabs/Update/_1200.php

<?php

namespace Zotlabs\Update;

class _1200 {
function run() {

	if(ACTIVE_DBTYPE == DBTYPE_MYSQL) {
		$r = q("ALTER TABLE item 
			DROP INDEX item_type,
			ADD INDEX uid_item_type (uid, item_type)
		");

		if($r)
			return UPDATE_SUCCESS;
		return UPDATE_FAILED;
	}
	else {
		return UPDATE_SUCCESS;
	}

}

}
refactor of the DB update system. Updates are now stored individually in Zotlabs/Update/_nnnn.php and are objects; so only the pending updates need to be loaded and executed rather than all historical updates. There is one single number (DB_UPDATE_VERSION) representing the current version and it is EQUAL TO the last known update. A dummy update _1201 was created to address the difference in counting behaviour; it will be executed on the next change of DB_UPDATE_VERSION as well as the next update. The database config values are also loaded from disk on every update immediately before setting the update lock in order to reduce timing conflicts and race conditions. 2018-02-16 20:42:02 +00:00			`<?php`

			`namespace Zotlabs\Update;`

			`class _1200 {`
			`function run() {`

			`if(ACTIVE_DBTYPE == DBTYPE_MYSQL) {`
			`$r = q("ALTER TABLE item`
			`DROP INDEX item_type,`
			`ADD INDEX uid_item_type (uid, item_type)`
			`");`

updates 1201 and 1200 should return success for postgres. notifications: remove class show and session storage entry when we mark all notifications seen 2018-02-19 19:23:13 +00:00			`if($r)`
			`return UPDATE_SUCCESS;`
			`return UPDATE_FAILED;`
			`}`
			`else {`
refactor of the DB update system. Updates are now stored individually in Zotlabs/Update/_nnnn.php and are objects; so only the pending updates need to be loaded and executed rather than all historical updates. There is one single number (DB_UPDATE_VERSION) representing the current version and it is EQUAL TO the last known update. A dummy update _1201 was created to address the difference in counting behaviour; it will be executed on the next change of DB_UPDATE_VERSION as well as the next update. The database config values are also loaded from disk on every update immediately before setting the update lock in order to reduce timing conflicts and race conditions. 2018-02-16 20:42:02 +00:00			`return UPDATE_SUCCESS;`
updates 1201 and 1200 should return success for postgres. notifications: remove class show and session storage entry when we mark all notifications seen 2018-02-19 19:23:13 +00:00			`}`

refactor of the DB update system. Updates are now stored individually in Zotlabs/Update/_nnnn.php and are objects; so only the pending updates need to be loaded and executed rather than all historical updates. There is one single number (DB_UPDATE_VERSION) representing the current version and it is EQUAL TO the last known update. A dummy update _1201 was created to address the difference in counting behaviour; it will be executed on the next change of DB_UPDATE_VERSION as well as the next update. The database config values are also loaded from disk on every update immediately before setting the update lock in order to reduce timing conflicts and race conditions. 2018-02-16 20:42:02 +00:00			`}`

updates 1201 and 1200 should return success for postgres. notifications: remove class show and session storage entry when we mark all notifications seen 2018-02-19 19:23:13 +00:00			`}`