Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support databases with custom triggers #48

Open
saberraz opened this issue May 6, 2020 · 4 comments
Open

Support databases with custom triggers #48

saberraz opened this issue May 6, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@saberraz
Copy link
Contributor

saberraz commented May 6, 2020

I have a geopackage, which users edit in QGIS/Input. When they try to submit their changes, it cannot determine the changes and creates conflict.

The changes are to data (add/remove/edit features) and there is no schema change.
@saberraz saberraz added bug Something isn't working data corruption - sync failure - crash The most critical classification labels May 6, 2020
@PeterPetrik
Copy link
Contributor

does it have connected tables by foreign keys?

@saberraz
Copy link
Contributor Author

saberraz commented May 6, 2020 •
edited
Loading

Probably yes...I shares you the data.

@PeterPetrik PeterPetrik removed the data corruption - sync failure - crash The most critical classification label May 19, 2020
@PeterPetrik
Copy link
Contributor

This is caused by SpatiaLite database with some extra tables (and triggers on top of them). Geodiff reject to do a automatic rebase for databases with unknown triggers (right now it only accepts geopackage triggers)

@PeterPetrik PeterPetrik changed the title Geodiff is failing to compare two files and keeps creating conflict files Geodiff keeps creating conflict files for databases with custom triggers May 19, 2020
@PeterPetrik PeterPetrik added enhancement New feature or request and removed bug Something isn't working labels May 19, 2020
@wonder-sk wonder-sk changed the title Geodiff keeps creating conflict files for databases with custom triggers Rebase fails for databases with custom triggers May 19, 2020
@wonder-sk
Copy link
Contributor

We could investigate if we can relax the current rules a bit without compromising user data, e.g.:

@wonder-sk wonder-sk mentioned this issue May 19, 2020
Open
@wonder-sk wonder-sk changed the title Rebase fails for databases with custom triggers Support databases with custom triggers Feb 16, 2021
@PeterPetrik PeterPetrik mentioned this issue Jun 1, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wonder-sk @PeterPetrik @saberraz