Changes between Version 6 and Version 7 of TracDev/Proposals/AdvancedNotification/DatabaseSchema
- Timestamp:
- Dec 20, 2014, 7:57:14 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/Proposals/AdvancedNotification/DatabaseSchema
v6 v7 1 1 {{{#!box important 2 2 This page was a draft. See [wiki:TracDev/DatabaseSchema/NotificationSystem] page now. 3 4 Table `notify_watch` is still in draft state.5 3 6 4 The [#OpenQuestions Open questions] section might still contain unimplemented ideas. … … 39 37 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. 40 38 41 See [browser:psuter/trac/notification/model.py@advanced-notification-subscriptions.2#/ trac.notification.model.Subscription]39 See [browser:psuter/trac/notification/model.py@advanced-notification-subscriptions.2#/Subscription trac.notification.model.Subscription] 42 40 43 41 == Table `notify_watch` … … 61 59 Use the `trac.notification.model.Watch` model class to access this table. 62 60 63 See [browser:psuter/trac/notification/model.py@ advanced-notification-dbtable-notify_watch#/trac.notification.model.Watch]61 See [browser:psuter/trac/notification/model.py@T11869_notify_watch_table#/Watch trac.notification.model.Watch] 64 62 65 63 == Open Questions