Subscription to queries triggers notifications that do not match query

kazu2012 / persevere-framework

Automatically exported from code.google.com/p/persevere-framework

0 stars 0 forks source link

Subscription to queries triggers notifications that do not match query #164

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

Subscribe to a query, but you will get notifications for all data changes in 
the table.

Original issue reported on code.google.com by kris...@gmail.com on 5 May 2009 at 11:07

GoogleCodeExporter commented 8 years ago

Original comment by kris...@gmail.com on 5 May 2009 at 11:09

Added labels: Effort-Low, Priority-High, Type-Defect

GoogleCodeExporter commented 8 years ago

This is fixed for normal queries, although some aggregate queries may still 
additional 
work. I think it works well enough that it is no longer high priority.

Original comment by kris...@gmail.com on 31 May 2009 at 3:49

Added labels: Effort-Medium, Priority-Low
Removed labels: Effort-Low, Priority-High

GoogleCodeExporter commented 8 years ago

There are other complexities within this, I'd like to know if you think are 
important enough to address. If I 
subscribe to a class with a query of ?enabled==true, then I should only see 
changes for entries with enabled set 
to true.  But also, if an entry has its enabled flag changed it should cause 
the subscription to react accordingly.  
This would be very useful for many apps. It does not seem to be part of the fix 
you applied, have you considered 
this case?

Original comment by pvolkaer...@gmail.com on 17 Jul 2009 at 7:47