David Fahlander

Thanks for circling back! It's great to hear that you found a way forward and I'm glad that my answer lead you in the right direction. I suppose this type...

Currently it's only possible to observe the query results and if they are encrypted, the encypted items is what will be observed. Decryption will have to happen on all items...

One side note: If using the option `{ cache: 'immutable' }` for the [Dexie constructor](https://dexie.org/docs/Dexie/Dexie) in [email protected], you could implement this optimization on your end because any instance that haven't...

Well it might be ways to avoid looping the records, but it's almost a no-op to loop over thousands of record to just check against a WeakMap. In [this snippet](https://jsitor.com/iFUFoqVYcfDL)...

It depends on your concurrancy requirements, size of database and memory consumption limits for small devices. If a user loads everything to memory in one tab, leave it open and...

> ... > So I am thinking the following steps could be the best path forward: > > 1. refactor from having 1 Table into 2 Tables, with the Array...

Don't see what error you get. There's a [section in the docs of liveQuery](https://dexie.org/docs/liveQuery()#rules-for-the-querier-function) you should read - specifically to do Promise.resolve() or Dexie.waitFor() around promises returned from web crypto...

Sorry pasted the wrong link. Should be https://dexie.org/docs/liveQuery()#rules-for-the-querier-function

The only option is to query the entire result and do the sorting in your app or library.

> I'm confused by this transformation. I don't know what `rerender` is, but I don't see any reason to expect it to be called in the `'id'` context - it...