Oghenovo Usiwoma

A potential solution here is to emit events for replication

@wtrocki We can easily use [traverse](https://www.npmjs.com/package/traverse) to update queue and save to storage. Ideally, the entire id swapping should run exclusively on storage or in a transaction but, for now,...

@wtrocki @kingsleyzissou I reopened this issue. I didn't realize it had been closed. I changed the title to more clearly reflect the topic.

@wtrocki @kingsleyzissou There are two major things I'm going to do to allow predicates use indexes (IDBKeyRange for Indexeddb); - Add field index information to predicate definitions; currently, the predicates...

> -1. Any reason for platform-specific? Indexes work differently on different platforms. We have to executor function for each platform that makes use of that platform's Indexes. For example, IndexedDB...

> What do you mean by this? I'm not sure if we should extend existing predicates. I'm not really extending them. I just want to add index information so the...

> Question is is it possible to utilize those from query side? I'm not sure how we will do this on the IDB side, but it's probably possible on the...

All query operations are performed on-device storage so, it's generally fast, plus fetching by id uses the "id" index. Advanced filtering capabilities require O(n) time on Indexeddb where "n" is...

@wtrocki On the matter of performance in relationships, I think we can speed up an operation like the one we have below by indexing the `userId` field on `Comment` ```...

I tried implementing and ran into some problems: - If the document subscribed to, is updated such that it no longer matches the filter you subscribe to then you will...