Keep sync running if some connections have a problem

Open
#80 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No file or test is named in the issue. Start at the db-sync tool's multi-connection synchronization entry point, trace how a connection failure is handled, and verify that later connections still sync while the failed one is reported without aborting the run.

Written by the indexing model from the issue text.

Description

enhancement

Right now, if there are multiple connections defined and one of them fails to sync for some reason, the whole sync stops. It would be nice if db-sync tool would be less strict and it could tolerate some failing connections.

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.