db-sync backward compatibility

Open
  • Is something wrong?
#469 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
databases, testing

Research direction

Start by locating the db-sync tests and migration entry points in this repository, then determine which two versions the issue is intended to cover. Add regression coverage showing that migration between those versions preserves the existing database without dropping it; done means the compatibility test passes.

Written by the indexing model from the issue text.

Description

db-sync

Migrate one version of db-sync to another. This should be possible without dropping the existing db.

Dominant language
Python
Stars
59
Forks
28
Avg merge
13h 57m
Merged PRs (30d)
87

Getting set up

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 IntersectMBO/cardano-node-tests

All issues in IntersectMBO/cardano-node-tests

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.