OpenSlides / OpenSlides/openslides-backend
[DaMMi] Implement proper migration framework
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 40
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 19
Description
For the sake of being able to quickly write migrations for the db, there should be a systematic way in which we bring new migrations into the system.
This is something we should tackle rather soon, since sometimes the necessity for a migration comes completely out of the left field.
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
The issue names no files, tests, or entry points. Start by surveying how database changes are currently handled in the backend, then define the framework's scope and acceptance criteria before implementation; done should mean migrations can be added systematically and used for unexpected database changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100