playframework / playframework/play-slick
Generate migration script incrementally?
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 794
- Forks
- 272
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 17
Description
play-slick seems only able to generate an initial SQL script..
For example, after it generates 1.sql, if I make a change to that slick Table, as I known, play-slick seems only able to regenerate a new 1.sql instead of append a 2.sql to the evolution..
This looks not very convenient because it will drop current table and clean all existing rows.. Would it be possible for play-slick to generate a new SQL script?
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, tests, or entry points are named. Start by tracing how play-slick generates 1.sql from a changed Slick Table and how evolution numbering is handled; done means a later change produces a new SQL script without dropping existing rows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100