-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
QFieldSync logs when synchro not successful #577
Comments
It would be great to have this enhancement. In my case I accitentally recognized, that some point-features were SILENTLY NOT added to database during syncronizing-process via cable. (Primary reason for failing syncronisation was a invalid/double sequence-number of unique id (for what reason ???)) Missing warnings will reduce trust in data extremly. (With warning-messages some import-issues may be fixed manually afterwards - but without warning-message the data may be corrupted by loss of some features) .... |
Hi!
I use QfieldSync to synchronise field data from several tablets with a Postgis database.
Overall, the synchronisation works well, but sometimes I noticed incomplete synchro (some entities are missing from the Postgis tables).
I realised that this was due to database uniques constraints that had not been respected, so it's normal that some entities couldn't be recorded in database.
However, QFieldSync does not return any error messages to the user.
Would it be possible to return the postgres logs when there are errors during synchronisation?
The text was updated successfully, but these errors were encountered: