Confirmed users
574
edits
Support/Notifications: Difference between revisions
Apparently Edit bases you off whatever rev you were looking at at the time. Surprise!
(Apparently Edit bases you off whatever rev you were looking at at the time. Surprise!) |
|||
| Line 72: | Line 72: | ||
== Iteration 3: More normalization, yielding better queryability: orthogonality of path elements (not just hierarchy) is possible without ridiculously inefficient substring queries. I don't think the joins would be too bad, but benches would be nice. == | == Iteration 3: More normalization, yielding better queryability: orthogonality of path elements (not just hierarchy) is possible without ridiculously inefficient substring queries. I don't think the joins would be too bad, but benches would be nice. Maintains ref integ of content type and object. == | ||
watches | watches: | ||
id content_type object_id event_type user/email/whatever | id content_type object_id event_type user/email/whatever | ||
1 15 2345 UntranslatedEvent | 1 15 2345 UntranslatedEvent | ||
watch_elements: | watch_elements: | ||
watch_id name value (int for size/speed/ad hoc joins) | watch_id name value (int for size/speed/ad hoc joins) | ||
1 lang CRC32(de) # Postgres doesn't have a CRC32 function, so ad hoc joins on string keys would be a pain. | 1 lang CRC32(de) # Postgres doesn't have a CRC32 function, so ad hoc joins on string keys would be a pain. | ||
1 localizable 1 | 1 localizable 1 | ||
1 approved 1 | 1 approved 1 | ||
on UntranslatedEvent for object_id=2345 and content_type=15: | on UntranslatedEvent for object_id=2345 and content_type=15: | ||