Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Optional extra checks for content of "base" schema

Open
#161 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
postgresql, python
Domain
databases

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.

Description

enhancement

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)

Dominant language
Python
Stars
53
Forks
24
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/db-sync

All issues in MerginMaps/db-sync

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.