paul@1089 | 1 | = File Store = |
paul@1089 | 2 | |
paul@1089 | 3 | The file data store is the default mechanism for storing calendar objects and |
paul@1089 | 4 | free/busy details, making use of various directories as described in the |
paul@1089 | 5 | [[../FilesystemUsage|filesystem usage guide]]. |
paul@1089 | 6 | |
paul@1089 | 7 | Benefits of the file store include transparency and ease of administration: |
paul@1089 | 8 | all data is stored in text files, direct modification of certain files can be |
paul@1089 | 9 | performed to change the system's behaviour, archiving is possible using |
paul@1089 | 10 | traditional filesystem tools. However, the simple representation may make |
paul@1089 | 11 | certain operations costly, such as the modification of tabular data, and |
paul@1089 | 12 | querying of data may not always be particularly convenient. |
paul@1089 | 13 | |
paul@1089 | 14 | Thus, the [[../DatabaseStore|database store]] exists as an alternative, offering |
paul@1089 | 15 | different characteristics to those of the file store. |