Nikolas Poniros

Generally speaking there is no reason why the sync-client shouldn't be able to work with angular. What you are experiencing is probably [this dexie issue](https://github.com/dfahlander/Dexie.js/issues/589). The sync-client still uses a...

I published 1.0.0-beta.10 of sync-client with the latest dexie versions. Check that out and let me know if the issue is fixed.

First off: no there is no Dexie.Syncable github issue regarding this flag (at least I didn't see any). The flag is the 4th parameter to the `applyRemoteChanges` function and it...

@dfahlander thanks for the input. Just to be clear my questions in the previous post are for the changes table in the server. I guess if the client sends a...

@nevf well in some sence this is what the changes table does. If a delete change is no longer in the table then how do I inform the client about...

@nevf this is what I did before both on the server and the client (older versions of the sync server and sync client). So if I understand correctly you want...

If the server already has an object and we don't have information about updates (effectively we have a create change) which will be the case if the changes table is...

No I haven't tested with multiple browsers yet. My first suspicion would be that you are missing the clientIdentity (or that the server is doing something stupid with it). You...

Hmm `nextClientID` should be 6 and not 1 nevertheless you did get the correct IDs for the clients assuming that you did use 5 different browsers. I will try to...

@nevf So I did a quick test with 2 different browsers. Everything seems to be working fine. At least the server communication passed the data that I expected, the changes.table...