Setting "Relation reference" on fk table break syncronization on project
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
No source file or test is named. Reproduce the issue with a QGIS 1:n relation using a "Relation reference" field, delete the parent geometry, and synchronize twice. Trace how the GeoPackage deletion is recorded and verify that the local-changes list clears and the second synchronization completes without the "delete nothing" error.
Written by the indexing model from the issue text.
Description
Hello there,
Sorry if this isn't the right place—I just wanted to share something I discovered.
First off, thank you for the Mergin Maps platform—it's a wonderful project!
I noticed an issue when using a table as a 1:n relationship (for example, a table containing images linked to geometry points).
If you set the field type to "Relation reference" in the QGIS layer properties (which seems like the correct choice), and then delete the parent geometry object and synchronize from the app, no errors are reported. The geometry feature and its related record are both deleted correctly (I checked this in the GPKG database).
However, if you check the "local changes" in the Mergin Maps app, you'll see that the feature deletion is still listed. Then, when you try to synchronize again, an error saying "delete nothing" appears, and synchronization becomes stuck from that point onward.
Changing the property of the foreign key related field in QGIS from "Relation reference" to "Text" seems to resolve the issue.
Thanks and kind regards,
Rob
- Dominant language
- Python
- Stars
- 185
- Forks
- 22
- Avg merge
- 1h 31m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/geodiff
-
GEODIFF_changesCount aborts the process on a truncated changeset (uncaught GeoDiffException)Possibly taken @mohanedmoh claimed this 21 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MerginMaps/geodiff#272 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MerginMaps/geodiff#275 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 46/100
MerginMaps/geodiff#274 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 40/100
MerginMaps/geodiff#267 ·
-
bug data corruption - sync failure - crash
Difficulty 4/5 3-5 days Newbie friendliness 48/100
MerginMaps/geodiff#255 ·
All issues in MerginMaps/geodiff
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Deltares/numba_celltree#100 · 1 comment ·
-
auto-reported bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
soup airgap-bundle --bundle-size-cap nan, inf or a cap above ~1.67e299 GiB stops with an internal ValueError/OverflowError (exit 1) instead of a usage errorPossibly taken @Keshemir claimed this today. Openbug claimed difficulty:2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MakazhanAlpamys/Soup#3045 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dagster-io/skills#80 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day