You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding this question so that we can continue this discussion. In my current project i have have a few migrations (with semver2 custom versioning, which may or may not be needed). During development i started with:
vNext/TableA.sql, vNext/TableB.sql
Moved both files to Migrations/1.0.0
Released a version into a test environment where mode = LiveField, Set mode = Brownfield locally
Later on found some mistakes, added vNext/NewColumnOnTableA.sql, vNext/NewIndexOnTableB.sql
Moved both scripts into Migrations/1.0.0 and made a new Release → 💣 Wouldn't allow this neither in brownfield or livefield.
I instead created a custom versioning like so:
Migrations/1.0.0-rc.1
Migrations/1.0.0-rc.3
Migrations/1.0.0-rc.7 (used to be vNext before release)
The problem is that i'm note quite sure if i'm using the right mode. Technically i would have liked to introduce the scripts (rc.3 and rc.7) as patch versions, however GWM doesn't recognize patch versions out of the box. Maybe i'm thinking about this wrong?
The text was updated successfully, but these errors were encountered:
Adding this question so that we can continue this discussion. In my current project i have have a few migrations (with semver2 custom versioning, which may or may not be needed). During development i started with:
vNext/TableA.sql
,vNext/TableB.sql
Migrations/1.0.0
LiveField
, Set mode =Brownfield
locallyvNext/NewColumnOnTableA.sql
,vNext/NewIndexOnTableB.sql
I instead created a custom versioning like so:
Migrations/1.0.0-rc.1
Migrations/1.0.0-rc.3
Migrations/1.0.0-rc.7
(used to bevNext
before release)The problem is that i'm note quite sure if i'm using the right mode. Technically i would have liked to introduce the scripts (rc.3 and rc.7) as patch versions, however GWM doesn't recognize patch versions out of the box. Maybe i'm thinking about this wrong?
The text was updated successfully, but these errors were encountered: