MerginMaps / MerginMaps/db-sync
Optional extra checks of "modified" schema after pull/push
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
For troubleshooting, it may be useful to have an option that would do an extra sanity check after each pull/push - it would verify that:
- comparing geopackage at the latest version and the "modified" schema gives no changes
- comparing "modified" schema and "base" schema gives no changes
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 file or test is named. Start by locating the pull and push entry points and the existing schema-comparison logic; then determine where an opt-in check can run after each operation. Done means the option verifies both requested comparisons and reports any changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100