David Fahlander
David Fahlander
> Thanks then we have 2 solutions for this. > > 1. await everything properly otherwise we might face these issues. > 2. Use "tx" input of transaction callback so...
sorry for late reply. Even if the fetchTokens callback expects a Promise of a TokenResponse in return, there's nothing requiring this to be returned immediately. You can implement any custom...
As sortBy is only a shortcut for toArray().then(a => a.sort(...)), you can do it like this instead: ```js where({}).offset(...).limit(num).toArray().then(a => a.sort((a,b) => a.yourProp < b.yourProp ? -1 : 1); ```...
Such a query might not be optimal even in an SQL database due to the limitation of how btree indexes works. There are different strategies. If your database is large...
It's in the [road map](https://dexie.org/roadmap/dexie5.0#richer-queries). That said, there can be trade-offs in performance to in ***any database*** to request an ordered result since the planner will have to choose whether...
The warning logs from dexie are not thrown errors but console.warning() when dexie need to workaround a situation that can occur on Chrome. In this case we get a similar...
I put a comment on one of the webkit issues this regards to, https://bugs.webkit.org/show_bug.cgi?id=273827, but that one is closed in belief of this having been resolved in iOS 17.6. [Alexey...
I still think you should be using liveQuery and use the `{cache: 'immutable'}` option in [Dexie constructor](https://dexie.org/docs/Dexie/Dexie). Within the callback of liveQuery you could query both tables according to your...
> Thanks. The querier I provide to useLiveQuery can only observe a single table though, right? So I'll need two useLiveQuery statements, each one will look at both tables and...
Hi! Thanks for the feedback! Currently there's no write-only access available, but if the forms stored as "private" objects (which is the default when not setting `realmId`) they will only...