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
In Flyway, baselineDescription ('<< Flyway Baseline >>') is configurable - although again looking more likely to lead to mass-breakage than to actually be a useful tunable.
Alongside, baselineVersion defaults to '1'. We instead default to zero, but this can be overridden by providing an argument to --init, and it also taken from the first schema-file encountered.
Should it be possible to configure a database in schema.conf for which there are no schema-files present, but where a baseline version is specified? This database would then be created with metadata but no further content.
I use-case might be to give a database baseline 'unmanaged', which would ensure that the database exists but would prevent further automated deployment to it - as opposed to having a database with a baseline schema-file only, which would allow higher-versioned schema to be added in the future.
Now massively useful, but it's a thought...
The text was updated successfully, but these errors were encountered:
In Flyway,
baselineDescription
('<< Flyway Baseline >>') is configurable - although again looking more likely to lead to mass-breakage than to actually be a useful tunable.Alongside,
baselineVersion
defaults to '1'. We instead default to zero, but this can be overridden by providing an argument to--init
, and it also taken from the first schema-file encountered.Should it be possible to configure a database in
schema.conf
for which there are no schema-files present, but where a baseline version is specified? This database would then be created with metadata but no further content.I use-case might be to give a database baseline 'unmanaged', which would ensure that the database exists but would prevent further automated deployment to it - as opposed to having a database with a baseline schema-file only, which would allow higher-versioned schema to be added in the future.
Now massively useful, but it's a thought...
The text was updated successfully, but these errors were encountered: