David Fahlander

Yes, order is guaranteed to be the same.

Regarding atomicy, this call should be made in a transaction. So a more correct code snippet would be: ```js const [keys, values] = await db.transaction('r', db.friends, () => Promise.all([ db.friends.toCollection().primaryKeys(),...

Thanks @parsagholipour . I updated the answer accordingly.

The old dexie-observable / dexie-syncable addons does use setImmediate in case it is present on the global object to fire off queue consumer. Probably JSzip puts its setImmediate onto the...

As always, you've nailed another multiEntry bug :) First time in liveQueries, then in the cache and now in dexie-cloud server. Every where...modify operation is re-executed on the server to...

A workaround until this is fixed would be to: ```ts const idsToDelete = await database.tagRelationships.where({ tags: tagid }).primaryKeys(); await database.tagRelationships.bulkDelete(idsToDelete); ``` ... just be aware that this would disable sync...

If it happens a fourth time we must add the badge ;) Hopefully this won't repeat (fingers crossed)

That would probably be an alternative to https://github.com/orgs/dexie/projects/4?pane=issue&itemId=71245732&issue=dexie%7CDexie.js%7C2003 I suppose. Sorry I have been very busy with the YJS support and all smaller FRs have stood back, but now that...

Yes, the sync end point would need support for some other use cases than what it's tailored for currently. I'd like to cherry pick the consistency features of it without...

The sync endpoint has it but it's still a bit verbose to use and no docs of it. Might add some lighter version of it maybe.