Database data migration
- Dominant language
- Go
- Stars
- 846
- Forks
- 128
- Avg merge
- 23h 7m
- Merged PRs (30d)
- 88
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](https://github.com/google/sam/pull/394/changes#r4013336707)_
Contributor guide
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.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100