Hi guys,
I've been trying to get Liquibase to run our changelog.xml using the
API. I found a piece of code that Nathan had made available to someone
at a previous time. It seems to work, mostly, but I get a SQLException
at the end of it all. Here's a code excerpt:
private void doLiquib
A little more info/revision:
I see now that the entire changelog.xml is *not* being performed. It
does, indeed, bail out on the first failure. I just don't understand
why, I guess. Here is the specific change set that is failing:
I'm not very familiar with HSQL or MySQL but is it possible that it's
complaining because the primary key (product_type) is indexed by
default? Oracle behaves this way.
On Mar 11, 2009, at 12:43 PM, David C. Hicks wrote:
> A little more info/revision:
>
> I see now that the entire changelog.
Nevermind, I misread the XML...
On Mar 11, 2009, at 12:58 PM, Peter Rebholz wrote:
> I'm not very familiar with HSQL or MySQL but is it possible that
> it's complaining because the primary key (product_type) is indexed
> by default? Oracle behaves this way.
>
>
> On Mar 11, 2009, at 12:43 PM,
I figured out the problem.
HypersonicSQL does not keep indexes as subordinates to their
corresponding tables. In our changelog.xml, we have indexes associated
with multiple tables for which the index has the same name. (ie. K_code
is an index name on tables A, B, and C). This works fine in m
t: Re: [Liquibase-user] How to debug upgrade called from API?
I figured out the problem.
HypersonicSQL does not keep indexes as subordinates to their
corresponding tables. In our changelog.xml, we have indexes associated
with multiple tables for which the index has the same name. (ie. K_code
is an
Original Message
> From: David C. Hicks
> To: liquibase-user@lists.sourceforge.net
> Sent: Wednesday, 11 March, 2009 19:53:23
> Subject: Re: [Liquibase-user] How to debug upgrade called from API?
>
> I figured out the problem.
>
> HypersonicSQL does not keep indexes as
ed to build the
database once rather than recreating over and over a clean one.
Paul
- Original Message
From: David C. Hicks
To: liquibase-user@lists.sourceforge.net
Sent: Thursday, 12 March, 2009 2:41:19
Subject: Re: [Liquibase-user] How to debug upgrade called from API?
That's
>
> - Original Message
> From: David C. Hicks
> To: liquibase-user@lists.sourceforge.net
> Sent: Thursday, 12 March, 2009 2:41:19
> Subject: Re: [Liquibase-user] How to debug upgrade called from API?
>
> That's not a bad idea, Paul. Thanks for the tip.
>
> My
sts.sourceforge.net
> Sent: Thursday, 12 March, 2009 2:41:19
> Subject: Re: [Liquibase-user] How to debug upgrade called from API?
>
> That's not a bad idea, Paul. Thanks for the tip.
>
> My solution ended up being somewhat hacked, but it works. In addition
> to our usual
Voxland, Nathan wrote:
> I was recently able to write a script to take a mysql dumpfile and
> load it into an h2 in-memory database. I have found h2 to be
> considerably faster than hsql in the liquibase unit tests.
>
>
Cool. I had not heard of H2, previously. I'll have to check that out.
T
C. Hicks
> To: liquibase-user@lists.sourceforge.net
> Sent: Thursday, 12 March, 2009 2:41:19
> Subject: Re: [Liquibase-user] How to debug upgrade called from API?
>
> That's not a bad idea, Paul. Thanks for the tip.
>
> My solution ended up being somewhat hacked, but it wo
gt;> the non supported things in HSQL). Although its not perfect because
>>> the databases will be different, if you can find a way to represent
>>> your types/indexes in HSQL then these settings will keep the
>>> specific changes away from production but still get t
t;
>>> In the past for database testing I've used DBUnit to clear out the
>>> database data and only insert what you wanted, effectively
>>> generating a database fixture. Its got little to do with Liquibase
>>> but its a nice neat way to deal with the data that functio
t;
>>>
>>>> In the past for database testing I've used DBUnit to clear out the
>>>> database data and only insert what you wanted, effectively
>>>> generating a database fixture. Its got little to do with Liquibase
>>>> but its a
15 matches
Mail list logo
