MerginMaps / MerginMaps/geodiff
Support databases with custom triggers
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 183
- Forks
- 21
- Avg merge
- 9d 11h
- Merged PRs (30d)
- 2
Description
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.
Contributor 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.
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the database change-detection path and its handling of custom triggers; done means feature edits in a GeoPackage are detected without a false conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100