Edgewall Software

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


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

Raise some questions about the proposed DB schema

Legend:

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

    v1 v2  
    2525Use the `trac.notification.model.Subscription` model class to access this table.
    2626
     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.
     28
    2729See [browser:psuter/trac/notification/model.py@advanced-notification-subscriptions#/ trac.notification.model.Subscription]
    2830
     
    4446
    4547See [browser:psuter/trac/notification/model.py@advanced-notification-subscription-attributes#/ trac.notification.model.SubscriptionAttribute]
     48
     49== Open Questions
     50
     51=== Rename `class` column?
     52
     53Something like `rule` might be more appropriate.
     54
     55See also [wiki:TracDev/Proposals/AdvancedNotification/INotificationSubscriber#Removeclassname INotificationSubscriber].
     56
     57=== Rename tables?
     58The current table names are taken from the th:AnnouncerPlugin.
     59
     60Would this cause problems for users that already used that plugin?
     61
     62=== Remove `time` and `changetime` columns?
     63These are not really needed.