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.

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

Allow more flexible baselines? #26

Open
srcshelton opened this issue Nov 3, 2016 · 0 comments
Open

Allow more flexible baselines? #26

srcshelton opened this issue Nov 3, 2016 · 0 comments

Comments

@srcshelton
Copy link
Owner

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant