On Thu, Dec 10, 2009 at 8:07 AM, Troy Kruthoff <[email protected]> wrote: > Currently, the etag returned when querying a view changes whenever the > database is updated regardless if the view was affected. Is it > planned/possible for the etag to represent the view instead of the database?
It is just a matter of some additional bookkeeping to track the last seq that changed the view. That would help with the Etags a bit. It isn't quite as good as etags that reflect the last update sequence within the query range. Those would be possible as well, but would require running a reduce calculation to generate the etag, which may or may not be worth it. > Is there anyway besides the etag to determine if the view data has changed? > > Thanks, > > Troy > > > -- Chris Anderson http://jchrisa.net http://couch.io
