Database data migration
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the storage code involved in database migration and the discussion in PR #394, especially the referenced change. Identify the migration portion that should be removed without designing its replacement; done means that storage no longer includes this drive-by migration work and the independent follow-up scope is clear.
Written by the indexing model from the issue text.
Description
at this point we are still in alpha and I think we can make this breaking change, I do not want to add data migration of a database as a drive by PR, just remove this part in storage and we tackle it independently with a better battery of tests ... this is a critical part that require its own design
Originally posted by @aojea in #394
- Dominant language
- Go
- Stars
- 926
- Forks
- 138
- Avg merge
- 11h 34m
- Merged PRs (30d)
- 117
Contributor guide
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 google/sam
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
PEP story Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1393 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
JakeChampion/lang#10213 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oasisprotocol/oasis-sdk#2523 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100