Just trying to update to 1.9.0 but I can't generate a changelog diff any
more.
Command line:
liquibase diffChangeLog --logLevel=DEBUG --baseDriver=org.postgresql.Driver
--baseUsername=xxx --basePassword=xxx
--baseUrl=jdbc:postgresql://localhost/xxx
liquibase.properties:
classpath=postgresql-8.
Try logLevel=FINEST
Nathan
On Jan 16, 2009, at 5:20 PM, "Dobes Vandermeer"
wrote:
>
> Just trying to update to 1.9.0 but I can't generate a changelog diff
> any
> more.
>
> Command line:
>
> liquibase diffChangeLog --logLevel=DEBUG --
> baseDriver=org.postgresql.Driver
> --baseUsername=x
Thanks - I set it to fine and instead of getting diagnostics the problem
just went away. Weird, but I'll accept it.
Voxland, Nathan wrote:
>
> Try logLevel=FINEST
>
> Nathan
>
>
>
> On Jan 16, 2009, at 5:20 PM, "Dobes Vandermeer"
> wrote:
>
>>
>> Just trying to update to 1.9.0 but I c
Strange. I wonder if the underlying error was "unknow log level "debug"
Nathan
On Jan 18, 2009, at 2:52 AM, "Dobes Vandermeer"
wrote:
>
>
> Thanks - I set it to fine and instead of getting diagnostics the
> problem
> just went away. Weird, but I'll accept it.
>
>
> Voxland, Nathan wrote:
That does seem likely - perhaps it's trying to log an error about the
invalid parameter, but the logging system has not been set up so it never
shows up.
Voxland, Nathan wrote:
>
> Strange. I wonder if the underlying error was "unknow log level "debug"
>
> Nathan
>
>
>
> On Jan 18, 2009, a
Actually now the problem has re-appeared, my current command line is:
liquibase diffChangeLog --logLevel=FINEST --baseDriver=org.postgresql.Driver
--baseUsername=xxx --basePassword=xxx
--baseUrl=jdbc:postgresql://localhost/xxx
I also tried no --logLevel and --logLevel=FINE but it just prints "M
Sorry about the spam, I thought it was running but it just ran enough to
print the errors:
Reading tables for ejb3unit @ jdbc:postgresql://localhost/ejb3unit ...
Reading foreign keys for ejb3unit @ jdbc:postgresql://localhost/ejb3unit ...
Reading primary keys for ejb3unit @ jdbc:postgresql://loca
That looks like a bug. I'll look more on Monday when I get back to my
computer.
Nathan
On Jan 22, 2009, at 2:18 PM, "Dobes Vandermeer"
wrote:
>
> Sorry about the spam, I thought it was running but it just ran
> enough to
> print the errors:
>
> Reading tables for ejb3unit @ jdbc:postgre
See: [ liquibase-Bugs-2525957 ] NPE at DiffResult while diffChangeLog on Oracle
https://sourceforge.net/tracker/?func=detail&atid=923443&aid=2525957&group_id=187970
--
Damian
--
This SF.net email is sponsored by:
Sourc
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
Do you get a stacktrace if you do logLevel=FINEST ?
Nathan
-Original Message-
From: halfempty [mailto:gnel...@hotmail.com]
Sent: Thursday, February 26, 2009 12:31 AM
To: liquibase-user@lists.sourceforge.net
Subject: Re: [Liquibase-user] diffChangeLog just prints "Migration F
11 matches
Mail list logo