HydrologicEngineeringCenter / HydrologicEngineeringCenter/cwms-database
[FLYWAY] Organize base schema migrations
Nobody has claimed this yet.
- Dominant language
- Visual Basic 6.0
- Stars
- 4
- Forks
- 8
- Avg merge
- 8d 20h
- Merged PRs (30d)
- 4
Description
The current organization of the versioned and repeatable scripts are there to support initial operations.
There needs to be a final organization before we "go live" with anything.
The after and before callbacks will likely remain as-is.
The versioned migrations should be organized into a folder and file names that match with and end up and the last version realized on the old process.
Likely
-VYYYY.MM.DD
|
+----V....
VYYYY.MM.DD__baseline.sql
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
Start by inspecting the Flyway versioned and repeatable migration scripts and identify the last version produced by the old process. Compare the existing versioned layout and filenames with that baseline, leaving the before and after callbacks unchanged. Done means the versioned migrations are organized under the intended folder and named through the old process's final version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100