Add property for excluding databases from changesets. #118

Merged
merged 1 commit into from Mar 18, 2013

Projects

None yet

2 participants

Similar to the dbms property for a changeset, sometimes it is easier
to just specify what databases shouldn't run a changeset.
Use property dbmsExclude to specify a list of databases that shouldn't
run a changeset.

Owner
nvoxland commented Mar 7, 2013

Rather than introducing another property, perhaps it would be better to add a "not" operator to the existing dbms attribute. So you would put dbms="!oracle" or dbms="-oracle" or "dbms="mssql,!oracle,h2"

What do you think?

I like that suggestion, I'll update the pull request.
On Mar 7, 2013 1:51 AM, "Nathan Voxland" notifications@github.com wrote:

Rather than introducing another property, perhaps it would be better to
add a "not" operator to the existing dbms attribute. So you would put
dbms="!oracle" or dbms="-oracle" or "dbms="mssql,!oracle,h2"

What do you think?


Reply to this email directly or view it on GitHubhttps://github.com/liquibase/liquibase/pull/118#issuecomment-14545503
.

@damienbiggs damienbiggs Add approach for excluding databases from running changesets.
Use ! to exclude a dbms.
E.g. to prevent oracle from running a changeset use dbms="h2,!oracle,mysql"
The changeset will run for h2 and mysql but not for oracle.
f377a11

Updated commit to use !
e.g. !oracle,h2

@nvoxland nvoxland merged commit 790dd3f into liquibase:master Mar 18, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment