Changes between Initial Version and Version 1 of TracDev/DatabaseSchema/NotificationSystem

Timestamp:

Dec 8, 2014, 7:39:58 PM (9 years ago)

Author:

Peter Suter

Comment:

—

TracDev/DatabaseSchema/NotificationSystem

@@ +1 @@
+[[PageOutline(2)]]
+
+= Trac Database Schema: Notification
+
+The TracNotification module stores notification event subscriptions in the database.
+
+== Table `notify_subscription`
+||'''Table'''||'''Key'''||
+||''notify_subscription''||''id''||
+
+||'''Columns'''||'''Type'''||'''Notes'''||
+||''id''||`auto_increment`|| ||
+||''time''||`int64`|| ||
+||''changetime''||`int64`|| ||
+||''class''|| || The name of the Python class that stored this subscription. ||
+||''sid''|| || The [wiki:TracDev/DatabaseSchema/Common#Tablesession session] ID of the subscriber. ||
+||''authenticated''||`int`|| `1` for authenticated session IDs, `0` for anonymous session IDs ||
+||''distributor''|| || Identifies the distributor to used for this subscription (e.g. `email`) ||
+||''format''|| || Identifies the MIME type to be used for this subscription (e.g. `text/plain` or `text/html`) ||
+||''priority''||`int`||Precedence level of this subscription. E.g. `1` overrules `2`. ||
+||''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.
+
+Use the `trac.notification.model.Subscription` model class to access this table. 
+
+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:trunk/trac/notification/model.py#/ trac.notification.model.Subscription]
+