Changes between Version 3 and Version 4 of TracDev/Proposals/AdvancedNotification/DatabaseSchema

Timestamp:

Nov 29, 2014, 6:29:12 PM (9 years ago)

Author:

Peter Suter

Comment:

Renamed table, added indices, updated links

TracDev/Proposals/AdvancedNotification/DatabaseSchema

@@ -5 +5 @@
 The TracNotification module stores notification event subscriptions in the database.
 
-== Table `subscription`
+== Table `notify_subscription`
 ||'''Table'''||'''Key'''||
-||''subscription''||''id''||
+||''notify_subscription''||''id''||
 
 ||'''Columns'''||'''Type'''||'''Notes'''||
@@ -21 +21 @@
 ||''adverb''|| ||`always` or `never`||
 
+||'''Indices'''||
+||''sid'', ''authenticated''||
+||''class''||
+
 Stores if a subscription rule always/never applies for a certain user, at what priority and using what distribution method/format.
 
@@ -27 +31 @@
 Note that this table does not store an (email) address, but the commonly used subscription tuple has an additional item `addr`. Usually such tuples that correspond to entries in this DB table contain a `addr` of `None`. Other tuples may contain an (email) address (e.g. retrieved from  a ticket CC field) but are missing the `sid` item instead.
 
-See [browser:psuter/trac/notification/model.py@advanced-notification-subscriptions#/ trac.notification.model.Subscription]
+See [browser:psuter/trac/notification/model.py@advanced-notification-subscriptions.2#/ trac.notification.model.Subscription]
 
 == Table `subscription_attribute`
@@ -64 +68 @@
 Would this cause problems for users that already used that plugin?
 
+DONE Renamed `subscription` to `notify_subscription`.
+
+TODO Rename `subscription_attribute` when it is implemented.
+
 === Remove `time` and `changetime` columns?
 These are not really needed.