Filtering by query and filtering by range do not have the same consequence on Observable notifications about dstore HOT 7 CLOSED

@cjolif, the intent is that it should only give you indices for items in the range. This sounds like a bug.

from dstore.

@cjolif, this is on my radar, but I haven't yet had time to resolve it.

from dstore.

@brandonpayton any progress on that one?

from dstore.

Hi @cjolif,

I had a chance to sit down with this tonight, and this turned out to be expected behavior. The crux of the issue is that dstore/Observable is not designed to enforce ranges. If an item is inserted in the middle of a tracked range, Observable will not notice that the insertion should cause the last item in the range to be removed because it no longer falls in the range, and if an item in a tracked range is removed from the store, Observable will not attempt to fetch the next item that would now fall in the range.

The expected use case is that range will be called after track to allow you to have a single change listener over a collection you are paging. You may call track on a ranged collection, but Observable will not enforce the range, only the filter and sort queries. This is somewhat confusing, and we are discussing changes that would make this clearer such as removing the range method and adding a fetchRange method that returns an array rather than a collection.

Thanks for your patience. I apologize for the confusion and the long response response time.

from dstore.

thanks a lot @brandonpayton. I guess this means I will have to ignore myself the notification coming outside of my range.

from dstore.

@cjolif, what is your use case for tracking a single range collection? It would be good for us to be familiar with in case we can help.

from dstore.

@brandonpayton maybe I myself wrongly assumed this use-case would make sense. Let me think more about this and come back to you.

from dstore.