Safety of ToCatchup?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.4k
- Forks
- 292
- PR merge metrics
- No merged PRs in 30d
Description
In the commit https://github.com/rubenv/sql-migrate/commit/a8bcd23c4ddffac12477ebb117c62fd208b334bc a number of years ago it was added to fill in the holes of steps that were not run even though the last migration is past already. How is this safe considering migration steps are not independent?
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.
Research direction
Start by reading commit a8bcd23c4ddffac12477ebb117c62fd208b334bc and tracing the ToCatchup behavior for skipped migration steps. Determine whether migration ordering and dependencies remain safe, then document the findings and agree on any required change or follow-up with the maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100