MerginMaps / MerginMaps/db-sync

Add include_tables option to DB Sync config

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

Nobody has claimed this yet.

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

Description

DB Sync currently supports skip_tables to exclude tables from synchronisation.

It would be great to add an include_tables option so users can explicitly define which tables should be synced from the database.

This would be useful when tables are added to a PostgreSQL schema, but only specific ones are intended for MerginMaps sync.

It would also make the sync process safer. At the moment, if new tables are added to the schema, they may automatically become part of the sync process. This can cause unexpected behaviour or potentially break the sync if the new tables are not intended or ready to be synced.

Example:

include_tables:
  - table_1
  - table_4
  - table_9

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.

Research direction

Start by locating the configuration handling for skip_tables and the sync logic that selects tables from the PostgreSQL schema. Add the documented include_tables option so only the listed tables are synchronized, then verify both explicit inclusion and the existing exclusion behavior with the project's configuration or sync tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql, python
Domain
databases
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.