Add some kind of database change managament solution to the backend
Open
Nobody has claimed this yet.
BACKEND
enhancement
priority: very low
- Dominant language
- Kotlin
- Stars
- 25
- Forks
- 6
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 9
Description
It would be beneficial to introduce Flyway of Liquibase or something similar to the project, because Hibernate can only do trivial migrations and the generated DDL is not always the most optimal.
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 reviewing the backend's current Hibernate schema-generation setup and how database changes are handled. Compare the proposed Flyway and Liquibase approaches against the project's migration needs and generated DDL concerns. Done means a migration solution has been selected and integrated, with its scope and verification documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, spring-boot
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100