Nabble - LiquiBase

Re: Update of DBUnit dataset documents

2008-09-04T13:01:33Z

Hi,

thanks for the quick answer. I am not sure about 1.) though; If e.g. a
new non-NULL column is introduced in schema version N+1, it wouldn't be
possible to insert a DBUnit dataset made for schema version N due to the
resulting constraint violations.

2.) sounds definitely possible, though it might be rather complex and
time-consuming, when updating a larger number of dataset files. And,
comments inserted in the dataset files to describe data for different
test cases e.g. would probably be lost.

So I think, it would be fantastic, if it were possible to update DBUnit
dataset files directly. What would be needed, was a new "adapter" for
LiquiBase, which supports DBUnit datasets as target (instead of another
RDMBS). Not all refactoring types would have to be supported by this
adapter, e.g. "Create Table" wouldn't be required.

Additionally, the schema version, for which a dataset file was made,
would have to be stored in each file to be updated, in order to know,
which change sets have to be applied. I don't know much about the
architecture of LiquiBase, so I can't estimate, how complex it would be
to add such a new target platform. Are you aware of any current efforts
underway to create any such integration of LiquiBase and DBUnit?

Cheers,

Gunnar

> I know of two strategies for now until some form of integration
> between the two tools
> happens (any good ideas what this should look like?).
>
> 1) DBunit can be made to ignore missing columns and be quite lax with
> its data imports and
> that tends to reduce the amount of errors you may see. This works when
> you have a lot of
> different test scenario files as you don't have to fix all of them,
> just the ones where the
> tables are very different.
>
> 2) Insert the test data into the old schema, run the liquibase upgrade
> and then re-export
> the test data.
>
> Paul K
>
> PS- You should not be unit testing with the database involved, that
> way leads to madness.
> Database involved tests should be called integration tests, unit tests
> are something very
> different.
>
> ----- Original Message ----
> From: Gunnar Morling <morling@ar...>
> To: liquibase-devel@li...
> Sent: Wednesday, 3 September, 2008 21:17:37
> Subject: [Liquibase-devel] Update of DBUnit dataset documents
>
> Hi there,
>
> right now I am playing around a bit with LiquiBase, and it really seems
> to be a very useful tool for schema migrations. I am curious though, how
> LiquiBase can manage the migration of master and test data.
>
> To be more concrete, in my setup, I use DBUnit XML dataset files to keep
> master data and common test data. As the schema changes over time (e.g.
> new non-NULL columns are introduced), these XML files are getting
> outdated and can't be executed against an updated DB, consequently
> leading to failing unit tests etc.
>
> So my question is, if there are any plans (or maybe it is already
> possible?) to support the migration of DBUnit dataset files with
> LiquiBase. Actually I think, those XML files can be regarded as a small
> snapshot of a database, so it should in general be possible to update
> them (when knowing, for which schema version they were created), using
> the schema changes described in a LiquiBase change set.
>
> Thanks a lot and kind regards,
>
> Gunnar Morling
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-devel mailing list
> Liquibase-devel@li...
> https://lists.sourceforge.net/lists/listinfo/liquibase-devel

From forum: LiquiBase - Development

Re: Now for my next completely stupid question. :-)

2008-09-04T12:40:23Z

Chris,

Thanks for the explanation of Contexts. I definitely had misunderstood
their inner workings. The other options would work, but they're not as
appealing for the reasons you stated. I *think* I'm about to get
permission to just start those guys on a fresh database and chalk this
one up to a development screw-up. It happens. :-) Fortunately, we're
early enough in our development cycle that it won't cause any great
problems. I was just hoping that we could avoid it.

Thanks to all for your input. It's much appreciated.

Dave

Chris Imershein wrote:

> David,
>
> There are a few different things that you could try:
>
> 1) Contexts
>
> As I understand them, contexts are actually a bit friendlier then you
> may think. (Caveat: I have not done my own testing with them yet, but
> I have looked at some of the source code).
>
> Anytime context is blank (on the command-line or in a changeSet),
> regular rules will apply to executing that changeSet (e.g. does it
> exist in the databasechangelog table yet, preconditions, etc).
>
> If you specify a context on the command line, and a changeSet has at
> least one context, AND it does not have a context that matches your
> target context, then the changeSet will be filtered out and skipped.
>
> So if you have a couple of changeSets marked "newCustomerContext" and
> some marked "qaContext" (and all other changeSets have no context),
> then if you run liquibase with "newCustomerContext" everything would
> get executed EXCEPT the "qaContext" changeSets (and vice versa).
>
> 2) Workaround with failOnError=false for failed precondition
>
> Until the new "onFail" precondition attribute setting is finished, you
> can do a workaround by setting "failOnError=false" on the changeSet
> itself. Then if the precondition fails, the changeSet will be skipped
> (but an entry will still be added to the databasechangelog table as if
> it had been run).
>
> The potential side effect is that if the change itself fails, that
> will not halt your migration update either.
>
> 3) Use runOnChange
>
> You could set runOnChange=true for the changeSets that have been
> changed. This would cause them to be rerun and the MD5 sum updated
> when necessary.
>
> However, this seems like it may provide less accurate historical
> information on which changes have really been applied. (Although as
> long as you have an old copy of the changeLog.xml file under your
> favorite change control system, you could revert back to get the
> original changeLog.xml file if needed).
>
> Hope that helps!
>
> Chris
>
>
> On Thu, Sep 4, 2008 at 3:26 PM, Voxland, Nathan
> <nvoxland@...
> <mailto:nvoxland@...>> wrote:
>
> The upcoming 1.8 release will have an onFail attribute that can be set
> on the changeSet's precondition tag to "HALT", "SKIP", or "WARN" to
> control what happens when the precondition fails. I'm hoping to have
> the final 1.8 release out by the end of next week.
>
> Nathan
>
> -----Original Message-----
> From: liquibase-user-bounces@...
> <mailto:liquibase-user-bounces@...>
> [mailto:liquibase-user-bounces@...
> <mailto:liquibase-user-bounces@...>] On Behalf
> Of David
> C. Hicks
> Sent: Thursday, September 04, 2008 1:54 PM
> To: liquibase-user@...
> <mailto:liquibase-user@...>
> Subject: Re: [Liquibase-user] Now for my next completely stupid
> question. :-)
>
> Thanks, Paul. Your explanation is what I expected to hear.
>
> What I'm facing is really a screw-up on the part of us developers.
> When
> we created our original changelog, we were using the Grails
> BootStrap to
>
> populate test data and also some domain data that is fairly
> static. That
>
> static data *should* have been put into the original changeset.
> Now, QA
> has a database with that static data, but we need to change some of it
> to different values, delete some, and insert some. However, on a new
> installation we would want to populate those tables. (Using several
> changesets to populate the new database works like a charm.) It's this
> special case of migrating the QA database that is causing my issues. I
> just need to keep one or two special changesets from executing if I'm
> migrating that particular database.
>
> First, I tried just modifying the original changesets. The checksum
> changed, though, so migration failed. Back to the drawing board...
> Next, PreConditions were attempted. As your email indicates, this
> didn't
>
> have the result that I thought I'd get. Onward...
> So, now I'm working out how to best put contexts to use for this same
> problem.
>
> Unless I've managed to get my head turned inside-out, I think I'm
> going
> to have to tag all of my changesets with a context, because if I
> specify
>
> a context on the command line it'll only run those tagged with that
> context. What I need is a way to say, "execute everything, but
> when it's
>
> the right circumstances DO NOT execute these two".
>
> Thanks again,
> Dave
>
>
> Paul Keeble wrote:
> > It does not quite work like that as you have gathered. Preconditions
> if they fail stop the entire migration, they don't just stop the
> changeset as you've determined. I think someone is working on a change
> for this which would allow you to skip a changeset rather than fail,
> I've certainly recently read on dev/user list some chat about failures
> and changes due for the next release. Whether its what you want I
> don't
> know. For now its doing what is implemented, but not what you want or
> expected.
> >
> > I'm not sure how you would go about skipping changesets except with
> the use of contexts and some external information choosing the
> contexts.
> Must admit I am not sure why pyou might want to do that, seems
> contract
> to good change control. If you could flesh out what your trying to
> do it
> might help find a workaround for now.
> >
> >
> > Paul
> >
> >
> > ----- Original Message ----
> > From: David C. Hicks <dhicks@...
> <mailto:dhicks@...>>
> > To: liquibase-user@...
> <mailto:liquibase-user@...>
> > Sent: Thursday, 4 September, 2008 19:29:55
> > Subject: [Liquibase-user] Now for my next completely stupid
> question.
> :-)
> >
> > Maybe it's not so stupid, but I hope so.
> >
> > I tried to use a <preCondition> to keep a changeSet from executing
> under
> > certain data sensitive circumstances using <sqlCheck>. The entire
> > migration fails, though, when the precondition is met. I may have
> > misunderstood, but I assumed that it would just skip that single
> > <changeSet>.
> >
> > Did I miss something, or am I interpreting the result incorrectly?
> >
> > Thanks,
> > Dave
> >
> >
> >
> ------------------------------------------------------------------------
> -
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> > Build the coolest Linux based applications with Moblin SDK & win
> great
> prizes
> > Grand prize is a trip for two to an Open Source event anywhere
> in the
> world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> <http://moblin-contest.org/redirect.php?banner_id=100&url=/>
> > _______________________________________________
> > Liquibase-user mailing list
> > Liquibase-user@...
> <mailto:Liquibase-user@...>
> > https://lists.sourceforge.net/lists/listinfo/liquibase-user
> >
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------
> -
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> > Build the coolest Linux based applications with Moblin SDK & win
> great
> prizes
> > Grand prize is a trip for two to an Open Source event anywhere
> in the
> world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> <http://moblin-contest.org/redirect.php?banner_id=100&url=/>
> > _______________________________________________
> > Liquibase-user mailing list
> > Liquibase-user@...
> <mailto:Liquibase-user@...>
> > https://lists.sourceforge.net/lists/listinfo/liquibase-user
> >
>
> ------------------------------------------------------------------------
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> <http://moblin-contest.org/redirect.php?banner_id=100&url=/>
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> <mailto:Liquibase-user@...>
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> <http://moblin-contest.org/redirect.php?banner_id=100&url=/>
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> <mailto:Liquibase-user@...>
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>

From forum: LiquiBase - User

Re: Now for my next completely stupid question. :-)

2008-09-04T12:26:17Z

David,

There are a few different things that you could try:

1) Contexts

As I understand them, contexts are actually a bit friendlier then you may think. (Caveat: I have not done my own testing with them yet, but I have looked at some of the source code).

Anytime context is blank (on the command-line or in a changeSet), regular rules will apply to executing that changeSet (e.g. does it exist in the databasechangelog table yet, preconditions, etc).

If you specify a context on the command line, and a changeSet has at least one context, AND it does not have a context that matches your target context, then the changeSet will be filtered out and skipped.

So if you have a couple of changeSets marked "newCustomerContext" and some marked "qaContext" (and all other changeSets have no context), then if you run liquibase with "newCustomerContext" everything would get executed EXCEPT the "qaContext" changeSets (and vice versa).

2) Workaround with failOnError=false for failed precondition

Until the new "onFail" precondition attribute setting is finished, you can do a workaround by setting "failOnError=false" on the changeSet itself. Then if the precondition fails, the changeSet will be skipped (but an entry will still be added to the databasechangelog table as if it had been run).

The potential side effect is that if the change itself fails, that will not halt your migration update either.

3) Use runOnChange

You could set runOnChange=true for the changeSets that have been changed. This would cause them to be rerun and the MD5 sum updated when necessary.

However, this seems like it may provide less accurate historical information on which changes have really been applied. (Although as long as you have an old copy of the changeLog.xml file under your favorite change control system, you could revert back to get the original changeLog.xml file if needed).

Hope that helps!

Chris

On Thu, Sep 4, 2008 at 3:26 PM, Voxland, Nathan <nvoxland@...> wrote:

The upcoming 1.8 release will have an onFail attribute that can be set
on the changeSet's precondition tag to "HALT", "SKIP", or "WARN" to
control what happens when the precondition fails. I'm hoping to have
the final 1.8 release out by the end of next week.

Nathan

-----Original Message-----
From: liquibase-user-bounces@...
[mailto:liquibase-user-bounces@...] On Behalf Of David
C. Hicks
Sent: Thursday, September 04, 2008 1:54 PM
To: liquibase-user@...

Subject: Re: [Liquibase-user] Now for my next completely stupid
question. :-)

Thanks, Paul. Your explanation is what I expected to hear.

What I'm facing is really a screw-up on the part of us developers. When
we created our original changelog, we were using the Grails BootStrap to

populate test data and also some domain data that is fairly static. That

static data *should* have been put into the original changeset. Now, QA
has a database with that static data, but we need to change some of it
to different values, delete some, and insert some. However, on a new
installation we would want to populate those tables. (Using several
changesets to populate the new database works like a charm.) It's this
special case of migrating the QA database that is causing my issues. I
just need to keep one or two special changesets from executing if I'm
migrating that particular database.

First, I tried just modifying the original changesets. The checksum
changed, though, so migration failed. Back to the drawing board...
Next, PreConditions were attempted. As your email indicates, this didn't

have the result that I thought I'd get. Onward...
So, now I'm working out how to best put contexts to use for this same
problem.

Unless I've managed to get my head turned inside-out, I think I'm going
to have to tag all of my changesets with a context, because if I specify

a context on the command line it'll only run those tagged with that
context. What I need is a way to say, "execute everything, but when it's

the right circumstances DO NOT execute these two".

Thanks again,
Dave

Paul Keeble wrote:
> It does not quite work like that as you have gathered. Preconditions
if they fail stop the entire migration, they don't just stop the
changeset as you've determined. I think someone is working on a change
for this which would allow you to skip a changeset rather than fail,
I've certainly recently read on dev/user list some chat about failures
and changes due for the next release. Whether its what you want I don't
know. For now its doing what is implemented, but not what you want or
expected.
>
> I'm not sure how you would go about skipping changesets except with
the use of contexts and some external information choosing the contexts.
Must admit I am not sure why pyou might want to do that, seems contract
to good change control. If you could flesh out what your trying to do it
might help find a workaround for now.
>
>
> Paul
>
>
> ----- Original Message ----
> From: David C. Hicks <dhicks@...>
> To: liquibase-user@...
> Sent: Thursday, 4 September, 2008 19:29:55
> Subject: [Liquibase-user] Now for my next completely stupid question.
:-)
>
> Maybe it's not so stupid, but I hope so.
>
> I tried to use a <preCondition> to keep a changeSet from executing
under
> certain data sensitive circumstances using <sqlCheck>. The entire
> migration fails, though, when the precondition is met. I may have
> misunderstood, but I assumed that it would just skip that single
> <changeSet>.
>
> Did I miss something, or am I interpreting the result incorrectly?
>
> Thanks,
> Dave
>
>
>
------------------------------------------------------------------------
-
> This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
> Build the coolest Linux based applications with Moblin SDK & win great
prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>
>
>
>
>
>
------------------------------------------------------------------------
-
> This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
> Build the coolest Linux based applications with Moblin SDK & win great
prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

From forum: LiquiBase - User

Re: Now for my next completely stupid question. :-)

2008-09-04T12:24:26Z

The upcoming 1.8 release will have an onFail attribute that can be set
on the changeSet's precondition tag to "HALT", "SKIP", or "WARN" to
control what happens when the precondition fails. I'm hoping to have
the final 1.8 release out by the end of next week.

Nathan

-----Original Message-----
From: liquibase-user-bounces@...
[mailto:liquibase-user-bounces@...] On Behalf Of David
C. Hicks
Sent: Thursday, September 04, 2008 1:54 PM
To: liquibase-user@...
Subject: Re: [Liquibase-user] Now for my next completely stupid
question. :-)

Thanks, Paul. Your explanation is what I expected to hear.

What I'm facing is really a screw-up on the part of us developers. When
we created our original changelog, we were using the Grails BootStrap to

populate test data and also some domain data that is fairly static. That

static data *should* have been put into the original changeset. Now, QA
has a database with that static data, but we need to change some of it
to different values, delete some, and insert some. However, on a new
installation we would want to populate those tables. (Using several
changesets to populate the new database works like a charm.) It's this
special case of migrating the QA database that is causing my issues. I
just need to keep one or two special changesets from executing if I'm
migrating that particular database.

First, I tried just modifying the original changesets. The checksum
changed, though, so migration failed. Back to the drawing board...
Next, PreConditions were attempted. As your email indicates, this didn't

have the result that I thought I'd get. Onward...
So, now I'm working out how to best put contexts to use for this same
problem.

Unless I've managed to get my head turned inside-out, I think I'm going
to have to tag all of my changesets with a context, because if I specify

a context on the command line it'll only run those tagged with that
context. What I need is a way to say, "execute everything, but when it's

the right circumstances DO NOT execute these two".

Thanks again,
Dave

Paul Keeble wrote:
> It does not quite work like that as you have gathered. Preconditions
if they fail stop the entire migration, they don't just stop the
changeset as you've determined. I think someone is working on a change
for this which would allow you to skip a changeset rather than fail,
I've certainly recently read on dev/user list some chat about failures
and changes due for the next release. Whether its what you want I don't
know. For now its doing what is implemented, but not what you want or
expected.
>
> I'm not sure how you would go about skipping changesets except with
the use of contexts and some external information choosing the contexts.
Must admit I am not sure why pyou might want to do that, seems contract
to good change control. If you could flesh out what your trying to do it
might help find a workaround for now.

>
>
> Paul
>
>
> ----- Original Message ----
> From: David C. Hicks <dhicks@...>
> To: liquibase-user@...
> Sent: Thursday, 4 September, 2008 19:29:55
> Subject: [Liquibase-user] Now for my next completely stupid question.

:-)
>
> Maybe it's not so stupid, but I hope so.
>
> I tried to use a <preCondition> to keep a changeSet from executing
under

> certain data sensitive circumstances using <sqlCheck>. The entire
> migration fails, though, when the precondition is met. I may have
> misunderstood, but I assumed that it would just skip that single
> <changeSet>.
>
> Did I miss something, or am I interpreting the result incorrectly?
>
> Thanks,
> Dave
>
>
>

> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>
>
>
>
>
>

------------------------------------------------------------------------
-
> This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
> Build the coolest Linux based applications with Moblin SDK & win great
prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

From forum: LiquiBase - User

Re: Now for my next completely stupid question. :-)

2008-09-04T12:10:46Z

One possibility is to inset a databasechangelog entry into the QA database so that liquibase thinks its already been exeucted. Next you go about either resetting all the data thats changed in a way that gets all environments to the right place (ie if its not there the delete gets zero rows etc). Alternatively since its static data you may just be able to do a changeset to delete the lot and then reinsert it.

The "hack" is manually adjusting the databasechangelog table, but its something I've had to do in the past one a team broke the change control on the database in a way that just totally broke the ability to upgrade it properly.

Paul
(You can get the entire line from a database it did run in correctly).

----- Original Message ----
From: David C. Hicks <dhicks@...>
To: liquibase-user@...
Sent: Thursday, 4 September, 2008 19:53:36
Subject: Re: [Liquibase-user] Now for my next completely stupid question. :-)

Thanks, Paul. Your explanation is what I expected to hear.

What I'm facing is really a screw-up on the part of us developers. When
we created our original changelog, we were using the Grails BootStrap to
populate test data and also some domain data that is fairly static. That
static data *should* have been put into the original changeset. Now, QA
has a database with that static data, but we need to change some of it
to different values, delete some, and insert some. However, on a new
installation we would want to populate those tables. (Using several
changesets to populate the new database works like a charm.) It's this
special case of migrating the QA database that is causing my issues. I
just need to keep one or two special changesets from executing if I'm
migrating that particular database.

First, I tried just modifying the original changesets. The checksum
changed, though, so migration failed. Back to the drawing board...
Next, PreConditions were attempted. As your email indicates, this didn't
have the result that I thought I'd get. Onward...
So, now I'm working out how to best put contexts to use for this same
problem.

Unless I've managed to get my head turned inside-out, I think I'm going
to have to tag all of my changesets with a context, because if I specify
a context on the command line it'll only run those tagged with that
context. What I need is a way to say, "execute everything, but when it's
the right circumstances DO NOT execute these two".

Thanks again,
Dave

Paul Keeble wrote:

> It does not quite work like that as you have gathered. Preconditions if they fail stop the entire migration, they don't just stop the changeset as you've determined. I think someone is working on a change for this which would allow you to skip a changeset rather than fail, I've certainly recently read on dev/user list some chat about failures and changes due for the next release. Whether its what you want I don't know. For now its doing what is implemented, but not what you want or expected.
>
> I'm not sure how you would go about skipping changesets except with the use of contexts and some external information choosing the contexts. Must admit I am not sure why pyou might want to do that, seems contract to good change control. If you could flesh out what your trying to do it might help find a workaround for now.
>
>
> Paul
>
>
> ----- Original Message ----
> From: David C. Hicks <dhicks@...>
> To: liquibase-user@...
> Sent: Thursday, 4 September, 2008 19:29:55
> Subject: [Liquibase-user] Now for my next completely stupid question. :-)
>
> Maybe it's not so stupid, but I hope so.
>
> I tried to use a <preCondition> to keep a changeSet from executing under
> certain data sensitive circumstances using <sqlCheck>. The entire
> migration fails, though, when the precondition is met. I may have
> misunderstood, but I assumed that it would just skip that single
> <changeSet>.
>
> Did I miss something, or am I interpreting the result incorrectly?
>
> Thanks,
> Dave
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

From forum: LiquiBase - User

Re: Now for my next completely stupid question. :-)

2008-09-04T11:53:36Z

Thanks, Paul. Your explanation is what I expected to hear.

What I'm facing is really a screw-up on the part of us developers. When
we created our original changelog, we were using the Grails BootStrap to
populate test data and also some domain data that is fairly static. That
static data *should* have been put into the original changeset. Now, QA
has a database with that static data, but we need to change some of it
to different values, delete some, and insert some. However, on a new
installation we would want to populate those tables. (Using several
changesets to populate the new database works like a charm.) It's this
special case of migrating the QA database that is causing my issues. I
just need to keep one or two special changesets from executing if I'm
migrating that particular database.

First, I tried just modifying the original changesets. The checksum
changed, though, so migration failed. Back to the drawing board...
Next, PreConditions were attempted. As your email indicates, this didn't
have the result that I thought I'd get. Onward...
So, now I'm working out how to best put contexts to use for this same
problem.

Unless I've managed to get my head turned inside-out, I think I'm going
to have to tag all of my changesets with a context, because if I specify
a context on the command line it'll only run those tagged with that
context. What I need is a way to say, "execute everything, but when it's
the right circumstances DO NOT execute these two".

Thanks again,
Dave

Paul Keeble wrote:

From forum: LiquiBase - User

Re: Now for my next completely stupid question. :-)

2008-09-04T11:44:05Z

It does not quite work like that as you have gathered. Preconditions if they fail stop the entire migration, they don't just stop the changeset as you've determined. I think someone is working on a change for this which would allow you to skip a changeset rather than fail, I've certainly recently read on dev/user list some chat about failures and changes due for the next release. Whether its what you want I don't know. For now its doing what is implemented, but not what you want or expected.

I'm not sure how you would go about skipping changesets except with the use of contexts and some external information choosing the contexts. Must admit I am not sure why pyou might want to do that, seems contract to good change control. If you could flesh out what your trying to do it might help find a workaround for now.

Paul

----- Original Message ----
From: David C. Hicks <dhicks@...>
To: liquibase-user@...
Sent: Thursday, 4 September, 2008 19:29:55
Subject: [Liquibase-user] Now for my next completely stupid question. :-)

Maybe it's not so stupid, but I hope so.

I tried to use a <preCondition> to keep a changeSet from executing under
certain data sensitive circumstances using <sqlCheck>. The entire
migration fails, though, when the precondition is met. I may have
misunderstood, but I assumed that it would just skip that single
<changeSet>.

Did I miss something, or am I interpreting the result incorrectly?

Thanks,
Dave

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

From forum: LiquiBase - User

Re: How to specify a context?

2008-09-04T11:36:01Z

Yep update way.

----- Original Message ----
From: David C. Hicks <dhicks@...>
To: liquibase-user@...
Sent: Thursday, 4 September, 2008 19:24:27
Subject: Re: [Liquibase-user] How to specify a context?

I finally found an example on Wikipedia. "context" is just an attribute
on the <changeSet> tag. That isn't very clearly documented. Am I allowed
to update the docs online?

David C. Hicks wrote:

> Yeah, I was aware of the command line switch. How do you specify that a
> particular change set is part of a given context, though? I see nothing
> about how to put the context name into the <changeSet>
>
>
> Paul Keeble wrote:
>
>> The bit of documentation you may be looking for is the command line guide: http://www.liquibase.org/manual/command_line
>>
>> about 60% down in the optional parameters it has –contexts=<value>ChangeSet contexts to execute
>> so you run it as liquibase --contexts=a,b,c ....
>> where a, b and c are contexts
>>
>> Paul
>>
>>
>>
>> ----- Original Message ----
>> From: David C. Hicks <dhicks@...>
>> To: liquibase-user@...
>> Sent: Thursday, 4 September, 2008 16:45:32
>> Subject: [Liquibase-user] How to specify a context?
>>
>> The online docs don't show how to specify a context. At least, I didn't
>> find anything that looked like it.
>> Can someone show me a quick example?
>>
>> Thanks,
>> Dave
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Liquibase-user mailing list
>> Liquibase-user@...
>> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>>
>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Liquibase-user mailing list
>> Liquibase-user@...
>> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>>
>>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>

From forum: LiquiBase - User

Now for my next completely stupid question. :-)

2008-09-04T11:29:55Z

Maybe it's not so stupid, but I hope so.

I tried to use a <preCondition> to keep a changeSet from executing under
certain data sensitive circumstances using <sqlCheck>. The entire
migration fails, though, when the precondition is met. I may have
misunderstood, but I assumed that it would just skip that single
<changeSet>.

Did I miss something, or am I interpreting the result incorrectly?

Thanks,
Dave

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

From forum: LiquiBase - User

Re: How to specify a context?

2008-09-04T11:26:44Z

Good point that does seem to be completely missing from the documentation!

Well according to the XSD its just an attribute on a ChangeSet called context:

<xsd:attributeGroup name="changeSetAttributes">
<xsd:attribute name="id" type="xsd:string"/>
<xsd:attribute name="author" type="xsd:string"/>
<xsd:attribute name="context" type="xsd:string"/>
<xsd:attribute name="dbms" type="xsd:string"/>
<xsd:attribute name="runOnChange" type="xsd:boolean"/>
<xsd:attribute name="runAlways" type="xsd:boolean"/>
<xsd:attribute name="failOnError" type="xsd:boolean"/>
</xsd:attributeGroup>
That is all there is too it believe. I think just like the command line it takes a list of contexts that are comma separated.
Paul

----- Original Message ----
From: David C. Hicks <dhicks@...>
To: liquibase-user@...
Sent: Thursday, 4 September, 2008 18:14:42
Subject: Re: [Liquibase-user] How to specify a context?

Yeah, I was aware of the command line switch. How do you specify that a
particular change set is part of a given context, though? I see nothing
about how to put the context name into the <changeSet>

Paul Keeble wrote:

> The bit of documentation you may be looking for is the command line guide: http://www.liquibase.org/manual/command_line
>
> about 60% down in the optional parameters it has –contexts=<value>ChangeSet contexts to execute
> so you run it as liquibase --contexts=a,b,c ....
> where a, b and c are contexts
>
> Paul
>
>
>
> ----- Original Message ----
> From: David C. Hicks <dhicks@...>
> To: liquibase-user@...
> Sent: Thursday, 4 September, 2008 16:45:32
> Subject: [Liquibase-user] How to specify a context?
>
> The online docs don't show how to specify a context. At least, I didn't
> find anything that looked like it.
> Can someone show me a quick example?
>
> Thanks,
> Dave
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-user mailing list
> Liquibase-user@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-user
>

From forum: LiquiBase - User

Re: How to specify a context?

2008-09-04T11:24:27Z

I finally found an example on Wikipedia. "context" is just an attribute
on the <changeSet> tag. That isn't very clearly documented. Am I allowed
to update the docs online?

David C. Hicks wrote:

From forum: LiquiBase - User

Re: How to specify a context?

2008-09-04T10:14:42Z

Yeah, I was aware of the command line switch. How do you specify that a
particular change set is part of a given context, though? I see nothing
about how to put the context name into the <changeSet>

Paul Keeble wrote:

From forum: LiquiBase - User

Re: How to specify a context?

2008-09-04T09:04:00Z

The bit of documentation you may be looking for is the command line guide: http://www.liquibase.org/manual/command_line

about 60% down in the optional parameters it has –contexts=<value>ChangeSet contexts to execute
so you run it as liquibase --contexts=a,b,c ....
where a, b and c are contexts

Paul

----- Original Message ----
From: David C. Hicks <dhicks@...>
To: liquibase-user@...
Sent: Thursday, 4 September, 2008 16:45:32
Subject: [Liquibase-user] How to specify a context?

The online docs don't show how to specify a context. At least, I didn't
find anything that looked like it.
Can someone show me a quick example?

Thanks,
Dave

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

From forum: LiquiBase - User

Oops...sorry!

2008-09-04T08:46:12Z

I only just realized that I sent my question about an error to the wrong
mailing list.
Sorry about that.
Dave

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-devel mailing list
Liquibase-devel@...
https://lists.sourceforge.net/lists/listinfo/liquibase-devel

From forum: LiquiBase - Development

How to specify a context?

2008-09-04T08:45:32Z

The online docs don't show how to specify a context. At least, I didn't
find anything that looked like it.
Can someone show me a quick example?

Thanks,
Dave

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Liquibase-user mailing list
Liquibase-user@...
https://lists.sourceforge.net/lists/listinfo/liquibase-user

From forum: LiquiBase - User