Radek Pietruszewski

yes, this is the expected behavior - locally changed columns win the conflict.

@davidmartos96 I would not recommend that. Synchronization is a very difficult problem, and when conflicts arise, by definition, there is no perfect way of automatically resolving that. It's possible to...

So cool @509dave16 !! ❤️ I have zero experience with Vue.js, so it's going to be difficult for me to judge the quality/correctness of the code (I know that for...

@509dave16 Yep, that works for me. Something like `withObservables` really doesn't need to be updated or maintained very often, so you releasing it under your own name would not be...

@509dave16 Hi! Is there any progress on this project?

@509dave16 Understood. Good luck with everything, and if you manage to get something working with the Vue recipe, i'm looking forward to that!

@rozPierog Check out `0.24.1-6`

https://github.com/Nozbe/WatermelonDB/blob/master/src/adapters/sqlite/index.js#L344 you can use this for running a raw query on the underlying database. However, you must be very careful as, by definition, a raw SQL query cannot know about...

> That means it might not be unique on the remote server. What do you mean by that? How would this non-uniqueness happen? > But I did not find any...

@netbull this was discussed in other issues already. Getting a conflict on a random ID is very, very unlikely. You can absolutely do sync-time ID remapping, but it's a huge...