Edgewall Software

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


Ignore:
Timestamp:
Oct 12, 2013, 5:28:31 PM (11 years ago)
Author:
Peter Suter
Comment:

Minor formatting fix

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/Proposals/AdvancedNotification/DatabaseSchema

    v2 v3  
    2525Use the `trac.notification.model.Subscription` model class to access this table.
    2626
    27 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.
     27Note 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.
    2828
    2929See [browser:psuter/trac/notification/model.py@advanced-notification-subscriptions#/ trac.notification.model.Subscription]
     
    5555See also [wiki:TracDev/Proposals/AdvancedNotification/INotificationSubscriber#Removeclassname INotificationSubscriber].
    5656
     57=== Rename `distributor` column?
     58
     59`transport` might be more consistent.
     60
    5761=== Rename tables?
    5862The current table names are taken from the th:AnnouncerPlugin.