1.1 --- a/docs/wiki/DatabaseStore Sat Oct 08 23:16:53 2016 +0200
1.2 +++ b/docs/wiki/DatabaseStore Sat Oct 08 23:45:25 2016 +0200
1.3 @@ -50,18 +50,18 @@
1.4 {{{#!table
1.5 '''Table''' || '''Purpose'''
1.6 ==
1.7 -`freebusy_other`
1.8 +`journal_freebusy_other`
1.9 || Period descriptions describing reservations for resources sharing a quota
1.10 .. (`store_user`) made by users or groups (`other`), structured similarly to the
1.11 .. `freebusy` table in the data store; this may be the same table as the one employed
1.12 .. by the data store to store received or deduced free/busy details
1.13 ==
1.14 -`freebusy_providers`
1.15 +`journal_freebusy_providers`
1.16 || Details of [[../EventRecurrences|recurring events]] for which new free/busy records
1.17 .. must be [[../CronIntegration|periodically generated]] because these events recur
1.18 .. indefinitely, selectable for each user (`store_user`)
1.19 ==
1.20 -`freebusy_provider_datetimes`
1.21 +`journal_freebusy_provider_datetimes`
1.22 || Date/time details associated with the `freebusy_providers` information
1.23 ==
1.24 `quota_delegates`
1.25 @@ -72,11 +72,21 @@
1.26 `quota_limits`
1.27 || A mapping from user identities or group identifiers to quota limits
1.28 ==
1.29 +`journal_objects`
1.30 +|| Records for each quota (`store_user`) containing received event data (`object_text`)
1.31 +==
1.32 +`journal_recurrences`
1.33 +|| Records for each quota (`store_user`) containing received recurrence event data
1.34 +.. (`object_text`)
1.35 +==
1.36 `user_groups`
1.37 || A mapping from user identities to group identifiers indicating the sharing of a quota
1.38 .. across a number of users
1.39 }}}
1.40
1.41 +The `journal_` prefix is employed for certain tables in order to allow the combination of
1.42 +the journal and store databases without each kind of data getting mixed up.
1.43 +
1.44 == Store Structure ==
1.45
1.46 The store information is retained in a collection of tables. Unlike the structure of
1.47 @@ -117,7 +127,7 @@
1.48 || Date/time details associated with the `freebusy_providers` information
1.49 ==
1.50 `objects`
1.51 -|| Records for each user (`store_data`) containing received event data (`object_text`)
1.52 +|| Records for each user (`store_user`) containing received event data (`object_text`)
1.53 ==
1.54 `requests`
1.55 || A collections of records, each belonging to a specific user (`store_user`)
1.56 @@ -126,6 +136,6 @@
1.57 .. indicating the availability of an incoming scheduling request for handling by a user
1.58 ==
1.59 `recurrences`
1.60 -|| Records for each user (`store_data`) containing received recurrence event data
1.61 +|| Records for each user (`store_user`) containing received recurrence event data
1.62 .. (`object_text`)
1.63 }}}