-
-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible bug in the moment of synchronization #54
Comments
Thanks for this feedback. To resolve it, I will introduce a breaking changes for the next version: Why I didn't use this technic before ? Because I used this end of sync timestamp as a kind of checkpoint: If we have such timestamp, we are sure the sync was finished, with no errors. In the next version, having two columns (begin / end of sync) will be a little be more tricky, but I think it will be enough to guarantee the sync involved is finished (or not) without (or with) errors. I'm actually work on this new behavior, expect a new version, very soon. But since it's a breaking changes, you will need to re-implement your whole sync architecture. Is it making sense ? Are you just testing (in this case, breaking changes are not an issue) ? Sebastien |
The most important thing is accurate synchronization. Anything to do in order to achieve this is accepted. At the moment, I'm just testing different situations to ensure it works smoothly before I use it in production. |
Is there any progress? |
Yep, i'm actually working on it :) |
hey @marjanoh2 |
I test database synchronization with 50 tables. Synchronization interval 30 seconds. I noticed that the changes that are made at the time of synchronization (1 -3 seconds) do not register as changes and then do not synchronize.
I made two videos to better understand the situation.
https://drive.google.com/open?id=1Gb4e9qjVwm5yzu_kv_n1oAFSv24QTN0m
https://drive.google.com/open?id=1yZ7dP10c968cXyucr5tCteRTB4ti0ksX
This is the code I use
{
The text was updated successfully, but these errors were encountered: