David Fahlander
David Fahlander
That's right, If indexedDB isn't present (as it normally is not in node unless polyfilled with fakeIndexedDB or indexedDBShim), it won't ever try to execute the given querier callback. Instead...
Please provide more context: * What code sample did you add? * Where, how did you add it?
Thank you for an interesting use case. The whole point with the less stricter version handling in dexie 4 is to be able to roll back to previous version. Currently,...
Just mentioning also the plans for dexie@5 to specify downgrade behavior, for example: ```ts db.version(3) .upgrade(async (tx) => { await tx.table('contacts')?.toCollection().modify((contact) => { const [firstName, lastName] = contact.displayName?.split(' ') ??...
That are wise ideas.
Good point for the docs. There's a lot to go through though. But I think sortBy() is quite special in that sense. All operations that, unlike sortBy(), return a promise...
Thanks! Looking into it
An update of a property will trigger all live querys that have requested that object no matter which properties they did access. This would be possible to track using Proxies...
I think that Dexie's responsibility should be restricted to not re-launch the querier too often and the frontend components responsibility would be to avoid unnescessary re-rendering based on comparing individal...
> Thanks. I'm not too familiar with the internals of dexie.js, would this theoretically require Dexie to also do O(n) operations for every key stroke, or could Dexie.js solve this...