MerginMaps / MerginMaps/db-sync
Optional extra checks for content of "base" schema
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
When troubleshooting sync issues, it would be useful to have an option to do extra checks of the "base" schema:
- at the end of each sync, db-sync could create some kind of checksum for each table in the base schema
- when syncing again, db-sync could verify that the base schema has not changed since the last run
(Currently we don't have that and when there are issues, it's hard to tell whether it is because something got changed in the database by some other party, or because there's a bug somewhere)
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
Start by tracing the db-sync synchronization flow and how it accesses the "base" schema. Determine how an optional per-table checksum could be stored and compared across runs, and consider the user-visible behavior when changes are detected; done means the option performs both checks without affecting default syncs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100