Migration meta issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by reviewing the existing migration implementation and the checked and unchecked items in this issue; done means documenting a process covering up and down migrations, batching schema changes, and major-version releases.
Written by the indexing model from the issue text.
Description
We should document a process for handling database migrations.
Requirements
- Support both up and down migrations. This may require maintaining the old queries.
- Try to batch schema changes into a single migration
- Migrations should happen in a major version release
Known issues
- #8
- #12
- #19
- Support wallets with 2+ keychains
- Dominant language
- Rust
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from bitcoindevkit/bdk-sqlite
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
bitcoindevkit/bdk-sqlite#11 ·
-
bitcoindevkit/bdk-sqlite#5 · 1 assignee ·
All issues in bitcoindevkit/bdk-sqlite
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
state:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
zed-industries/zed#64680 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
RustPython/RustPython#8802 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TheLarkInn/aipm#2390 ·