Option to just spit out a `.sql` file instead of actually doing updates on DB?
Open
Nobody has claimed this yet.
Sponsor needed
WishList
- Dominant language
- Common Lisp
- Stars
- 6.5k
- Forks
- 613
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
This would be useful when we want to simply generate the .sql file and do the upgrade elsewhere or maybe check-in the schema transformation file and use it in tests repeatedly.
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
No files, tests, or entry points are named in the issue. Start by tracing the command path that performs database updates and identify where an output-only option belongs. Done means the migration can emit a reusable .sql file without applying updates to the database, including coverage for repeated or checked-in use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100