Update TxObservers to filter by more complex criteria #213

New issue

Open

opened 2020-08-06 16:56:45 +00:00 by gburd · 0 comments

gburd commented

2020-08-06 16:56:45 +00:00

(Migrated from github.com)

For clients this might be - Providing an entid so a notification will only get fired for a specific record and not for all records that touch an attribute.

For materialized views this might be aggregation, negation or comparison logic, i.e. only notify me about transactions that have a value less than a constant, or that change number of times a url has been viewed.

Currently TxObservers only handle a set of matching attributes to filter whether it wants to be notified about a set of transactions. We need to be able to specify a set of filter criteria to further exclude notifications from an object. For clients this might be - Providing an entid so a notification will only get fired for a specific record and not for all records that touch an attribute. For materialized views this might be aggregation, negation or comparison logic, i.e. only notify me about transactions that have a value less than a constant, or that change number of times a url has been viewed.