streams/Zotlabs/Update/_1093.php

<?php

namespace Zotlabs\Update;

class _1093
{
    public function run()
    {
        $r = q("ALTER TABLE `chatpresence` ADD `cp_client` CHAR( 128 ) NOT NULL DEFAULT ''");
        if ($r)
            return UPDATE_SUCCESS;
        return UPDATE_FAILED;
    }


}
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;`

psr12 updates 2021-12-02 23:02:31 +00:00			`class _1093`
			`{`
			`public function run()`
			`{`
			$r = q("ALTER TABLE `chatpresence` ADD `cp_client` CHAR( 128 ) NOT NULL DEFAULT ''");
			`if ($r)`
			`return UPDATE_SUCCESS;`
			`return UPDATE_FAILED;`
			`}`
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

			`}`