Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | port db update improvements from zap | Mario Vavti | 2019-05-03 | 1 | -1/+8 |
| | |||||
* | refactor of the DB update system. Updates are now stored individually in ↵ | zotlabs | 2018-02-16 | 1 | -74/+60 |
| | | | | 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. | ||||
* | turn platform name and std_version into config variables | zotlabs | 2017-07-13 | 1 | -3/+5 |
| | |||||
* | issues from hubzilla:#737 | zotlabs | 2017-04-26 | 1 | -1/+1 |
| | |||||
* | provide compatibility with old-style update system | zotlabs | 2017-03-25 | 1 | -6/+16 |
| | |||||
* | get rid of 'davguest' and allow for project specific DB updates (currently ↵ | zotlabs | 2017-03-25 | 1 | -10/+14 |
| | | | | db updates are common between all possible projects/subprojects/forks). | ||||
* | move db_upgrade to zlib | zotlabs | 2017-03-23 | 1 | -0/+105 |