Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rename DbScripts_future to DbScripts_finalization #177

Merged
merged 3 commits into from
Oct 12, 2023
Merged

Rename DbScripts_future to DbScripts_finalization #177

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d733aca
Rename DbScripts_future to DbScripts_finalization
mimartin12 Aug 14, 2023
e79a386
Linting
mimartin12 Aug 16, 2023
e24d8a2
Merge branch 'master' into DEVOPS-1520-rename-dbo-future-and-db-scrip…
mimartin12 Sep 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/contributing/database-migrations/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,9 @@ required.
3. Write a new Migration and place it in `src/Migrator/DbScripts_finalization`. Name it
`YYYY-0M-FinalizationMigration.sql`.
- Typically migrations are designed to be run in sequence. However since the migrations in
DbScripts_future can be run out of order, care must be taken to ensure they remain compatible
with the changes to DbScripts. In order to achieve this we only keep a single migration, which
executes all backwards incompatible schema changes.
DbScripts_finalization can be run out of order, care must be taken to ensure they remain
compatible with the changes to DbScripts. In order to achieve this we only keep a single
migration, which executes all backwards incompatible schema changes.

### EF migrations

Expand Down