I have pretty much the same configuration as dobes. On 1.9.0 and 1.9.1 the
"diff" command works but "diffChangeLog" results in "Migration failed:
unknown reason". Version 1.8.1 works fine.
I see in the linked bug the fix was taken into 1.9.1 but the problem still
is there (for postgres anyway). I
I'm using postgres and trying to use diffChangeLog, and I find that it will
only diff the public schema. I have my own schema, and even if I pass it in
using --defaultSchema=myschema I still only get the diff for the public
schema. Any recommendations?
Thanks!
Paul Keeble wrote:
>
> I know I'v
gt;
> Nathan
>
> -----Original Message-
> From: halfempty [mailto:gnel...@hotmail.com]
> Sent: Thursday, February 26, 2009 12:46 AM
> To: liquibase-user@lists.sourceforge.net
> Subject: Re: [Liquibase-user] PostgreSQL and DB-Schemas
>
>
> I'm using postgre
Hi
I noticed a problem with 1.9. I used the generateChangeLog command on my
source DB to generate the following XML:
http://www.liquibase.org/xml/ns/dbchangelog/1.9";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog/1.9
http:
Thanks for replying, but nope -- the XML there is the entire DB. I created a
new DB and used update with the generated XML.
Alexandr Popov wrote:
>
> Do you have in you database another key, index, fk that use this columns
> "clusterkey, clustertype"??
> if you have can you show them ??
>
--
Ah -- interesting, I think you're right. When doing the diff, it will call
Set.contains() which relies on equals(). The other classes implement this,
but UniqueContstraint does not.
Can one of the LB developers take a look at this? Definitely looks like a
bug.
Thanks!
Damian Gołda wrote:
>
>
