2016-03-11 | Paul Boddie | raw annotate files changeset graph | Added support for store/journal-level locking to the PostgreSQL store. Fixed various journal and free/busy provider tables in the database schema. Fixed inappropriate slicing of free/busy providers when retrieving them from the store. Fixed some unparameterised database store queries. Added a store method for setting quota limits along with a tool used by the tests to configure them. Changed the tools to be more aware of different store types and updated the installation script. Added documentation about store types. Converted the remaining tests to work with the database store. Made a minimal common test configuration script so that the resource_request.sh script can use the common configuration without deleting state information. | freebusy-collections |
1 = File Store = 2 3 The file data store is the default mechanism for storing calendar objects and 4 free/busy details, making use of various directories as described in the 5 [[../FilesystemUsage|filesystem usage guide]]. 6 7 Benefits of the file store include transparency and ease of administration: 8 all data is stored in text files, direct modification of certain files can be 9 performed to change the system's behaviour, archiving is possible using 10 traditional filesystem tools. However, the simple representation may make 11 certain operations costly, such as the modification of tabular data, and 12 querying of data may not always be particularly convenient. 13 14 Thus, the [[../DatabaseStore|database store]] exists as an alternative, offering 15 different characteristics to those of the file store.