aboutsummaryrefslogtreecommitdiffstats
path: root/Zotlabs/Update
Commit message (Collapse)AuthorAgeFilesLines
* fix another pgsql update errorMario2018-04-301-1/+1
|
* Update issues on postgreszotlabs2018-04-303-3/+3
|
* fix any misconfigured channel permission limitszotlabs2018-04-201-0/+26
|
* missing update file in the previous update commitzotlabs2018-04-161-0/+26
|
* OAuth2 integrationzotlabs2018-04-031-0/+78
|
* fix syntax error in postgres updateMario2018-03-081-3/+3
|
* federated polls: GNU-Social requires us to preserve the original order of ↵zotlabs2018-03-071-0/+26
| | | | the poll answers for use in making a vote, unlike diaspora (which selects by guid) and activitypub (which selects by non-localisable text).
* federated polls: add poll_author which will be necessary for Diaspora federationzotlabs2018-03-061-0/+26
|
* update DB update 1205 to mitigateMario Vavti2018-03-021-0/+11
| | | | ERROR 1069 (42000): Too many keys specified; max 64 keys allowed
* db update to drop index resource_type. we have uid_resource_type now.Mario Vavti2018-03-021-0/+24
|
* typoMario Vavti2018-02-281-1/+1
|
* missed one index in the last updateMario Vavti2018-02-281-0/+24
|
* another DB upgrade to address some long running maintenance queriesMario Vavti2018-02-261-0/+27
|
* fix issues with DB update 1204Mario Vavti2018-02-231-3/+3
|
* provide DB compatibility for poll and voting implementations across several ↵zotlabs2018-02-221-0/+34
| | | | platforms
* missing fileMario Vavti2018-02-201-0/+29
|
* updates 1201 and 1200 should return success for postgres. notifications: ↵Mario Vavti2018-02-193-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 1202Mario Vavti2018-02-192-5/+28
|
* refactor of the DB update system. Updates are now stored individually in ↵zotlabs2018-02-16202-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.