Closed
Bug 623643
Opened 15 years ago
Closed 15 years ago
Skeletal watch data model
Categories
(support.mozilla.org :: General, defect, P1)
support.mozilla.org
General
Tracking
(Not tracked)
VERIFIED
FIXED
2.5
People
(Reporter: erik, Assigned: paulc)
References
Details
(Whiteboard: [qa-])
Pick and implement a model for storing watches. I favor Iteration 3 from https://wiki.mozilla.org/Support/Notifications; it provides a good tradeoff between ref integ (practically, Django should delete watches for us when a watched obj is deleted) and queryability. Whatever we choose should be able to fulfill all the triggering use cases on the wiki page.
Decide how to reference users (including anonymous ones) such that we can (1) keep using a user's current address as they update it and (2) pull anonymous watches into relationship if the owning user registers.
| Assignee | ||
Updated•15 years ago
|
Assignee: nobody → paulc
| Assignee | ||
Comment 1•15 years ago
|
||
Created branch here with the skeletons:
https://github.com/jsocol/kitsune/tree/notifications-623641
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 2•15 years ago
|
||
Please add QA steps or mark as [qa-], thanks
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•