Feature Request: Automatically Track Schema Changes and Generate Migration Code
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9.9k
- Forks
- 734
- Avg merge
- 6h 36m
- Merged PRs (30d)
- 8
Description
It appears that the SeaORM CLI tools do not automatically generate migration files when the database schema changes. Instead, developers are required to create and maintain migration files manually. This behavior can be error-prone and time-consuming, especially when schemas evolve frequently. Automatic or assisted migration generation based on schema changes would significantly improve the developer experience.
Contributor guide
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
No files or tests are named. Start by reviewing the SeaORM CLI migration workflow and existing migration-file handling, then determine how schema changes would be detected and represented. Done requires a defined, validated approach for automatically or assistively generating migration code.
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
- 25/100