Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | missed one index in the last update | Mario Vavti | 2018-02-28 | 1 | -0/+24 |
| | |||||
* | another DB upgrade to address some long running maintenance queries | Mario Vavti | 2018-02-26 | 1 | -0/+27 |
| | |||||
* | fix issues with DB update 1204 | Mario Vavti | 2018-02-23 | 1 | -3/+3 |
| | |||||
* | provide DB compatibility for poll and voting implementations across several ↵ | zotlabs | 2018-02-22 | 1 | -0/+34 |
| | | | | platforms | ||||
* | missing file | Mario Vavti | 2018-02-20 | 1 | -0/+29 |
| | |||||
* | updates 1201 and 1200 should return success for postgres. notifications: ↵ | Mario Vavti | 2018-02-19 | 3 | -8/+16 |
| | | | | remove class show and session storage entry when we mark all notifications seen | ||||
* | backport update 1201 to the new update system and move dummy update to 1202 | Mario Vavti | 2018-02-19 | 2 | -5/+28 |
| | |||||
* | refactor of the DB update system. Updates are now stored individually in ↵ | zotlabs | 2018-02-16 | 202 | -0/+4496 |
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. |