clockworklabs / clockworklabs/SpacetimeDB
Support manual migrations
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
I've read the documentation regarding incremental migrations. While that provides a few advantages, over time, it hinders maintainability a lot. It removes the ability to do small migrations often, and forces you to have multiple structs and code paths living at the same time, for very long. Over time, the code complexity becomes a problem.
For a lot of games, downtime is an acceptable tradeoff. Especially games that have the ambition to be maintained for a long time. So it would be great that SpacetimeDB also supports manual migrations!
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 the incremental migrations documentation and locating the existing migration entry points. The issue names no files or tests, so first clarify the expected manual-migration workflow, downtime behavior, and compatibility requirements; done should include documented behavior and coverage for the supported workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100