Streams/streams
Streams/streams
1
0
Fork 0
mirror of https://codeberg.org/streams/streams.git synced 2024-09-21 06:35:18 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
streams/Zotlabs/Update/_1152.php

54 lines
1.9 KiB
PHP
Raw Normal View History

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 _1152
{
public function run()
{
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
psr12 updates
2021-12-02 23:02:31 +00:00
if (ACTIVE_DBTYPE == DBTYPE_POSTGRES) {
$r1 = q("CREATE TABLE IF NOT EXISTS \"dreport\" (
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
\"dreport_id\" serial NOT NULL,
\"dreport_channel\" int(11) NOT NULL DEFAULT '0',
\"dreport_mid\" char(255) NOT NULL DEFAULT '',
\"dreport_site\" char(255) NOT NULL DEFAULT '',
\"dreport_recip\" char(255) NOT NULL DEFAULT '',
\"dreport_result\" char(255) NOT NULL DEFAULT '',
\"dreport_time\" timestamp NOT NULL DEFAULT '0001-01-01 00:00:00',
\"dreport_xchan\" char(255) NOT NULL DEFAULT '',
PRIMARY KEY (\"dreport_id\") ");
psr12 updates
2021-12-02 23:02:31 +00:00
$r2 = q("create index \"dreport_mid\" on dreport (\"dreport_mid\") ");
$r3 = q("create index \"dreport_site\" on dreport (\"dreport_site\") ");
$r4 = q("create index \"dreport_time\" on dreport (\"dreport_time\") ");
$r5 = q("create index \"dreport_xchan\" on dreport (\"dreport_xchan\") ");
$r6 = q("create index \"dreport_channel\" on dreport (\"dreport_channel\") ");
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
psr12 updates
2021-12-02 23:02:31 +00:00
$r = $r1 && $r2 && $r3 && $r4 && $r5 && $r6;
} else {
$r = q("CREATE TABLE IF NOT EXISTS `dreport` (
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
`dreport_id` int(11) NOT NULL AUTO_INCREMENT,
`dreport_channel` int(11) NOT NULL DEFAULT '0',
`dreport_mid` char(255) NOT NULL DEFAULT '',
`dreport_site` char(255) NOT NULL DEFAULT '',
`dreport_recip` char(255) NOT NULL DEFAULT '',
`dreport_result` char(255) NOT NULL DEFAULT '',
`dreport_time` datetime NOT NULL DEFAULT '0001-01-01 00:00:00',
`dreport_xchan` char(255) NOT NULL DEFAULT '',
PRIMARY KEY (`dreport_id`),
KEY `dreport_mid` (`dreport_mid`),
KEY `dreport_site` (`dreport_site`),
KEY `dreport_time` (`dreport_time`),
KEY `dreport_xchan` (`dreport_xchan`),
KEY `dreport_channel` (`dreport_channel`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 ");
psr12 updates
2021-12-02 23:02:31 +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
psr12 rewrites, continued
2021-12-03 03:01:39 +00:00
if ($r) {
psr12 updates
2021-12-02 23:02:31 +00:00
return UPDATE_SUCCESS;
psr12 rewrites, continued
2021-12-03 03:01:39 +00:00
}
psr12 updates
2021-12-02 23:02:31 +00:00
return UPDATE_FAILED;
}
psr12 rewrites, continued
2021-12-03 03:01:39 +00:00
}
Reference in a new issue Copy permalink