Re: [Liquibase-user] Dies on "SELECT ID FROM user WHERE 1 = 0"

Thanks. I'll get that change in. I'm hoping to have 1.9.1 out next week. Nathan On Feb 13, 2009, at 8:52 PM, "Robert Fischer" wrote: > Double quotes: "". > > ~~ Robert. > > Voxland, Nathan wrote: >> yes. The trouble is that our hsql database class does not specify a >> table escape method.

Re: [Liquibase-user] Dies on "SELECT ID FROM user WHERE 1 = 0"

Double quotes: "". ~~ Robert. Voxland, Nathan wrote: > yes. The trouble is that our hsql database class does not specify a > table escape method. > > Do you know what hsql uses to escape tables? > > Nathan > > > On Feb 13, 2009, at 5:50 PM, "Robert Fischer" > > wrote: > > > I'm not on p

Re: [Liquibase-user] Dies on "SELECT ID FROM user WHERE 1 = 0"

yes. The trouble is that our hsql database class does not specify a table escape method. Do you know what hsql uses to escape tables? Nathan On Feb 13, 2009, at 5:50 PM, "Robert Fischer" wrote: > I'm not on postgres -- I'm on hypersonic by way of p6spy. Could > this be causing a problem?

Re: [Liquibase-user] Dies on "SELECT ID FROM user WHERE 1 = 0"

I'm not on postgres -- I'm on hypersonic by way of p6spy. Could this be causing a problem? ~~ Robert. Voxland, Nathan wrote: > It should just be doing that if you are doing a diff. Just making sure > that is what you are doing and it is not making those calls on its > own... > > I checked and

Re: [Liquibase-user] Dies on "SELECT ID FROM user WHERE 1 = 0"

It should just be doing that if you are doing a diff. Just making sure that is what you are doing and it is not making those calls on its own... I checked and it looks like the call to the 1 = 0 statement is trying to escape the table name and the postgres Database class is coded to quote them co

Re: [Liquibase-user] Enlighten Me: Change Sets With Multiple Changes

Hi all, +1. During development it is convenient to write a sequence of changes and than play it against development database snapshot. Usually before doing that I'm marking the base change set with tag and rolling back to one. if some wrong is occurred. But more elegant is using the subsequent ch

[Liquibase-user] Dies on "SELECT ID FROM user WHERE 1 = 0"

When Liquibase fires up, I'm getting a whole series of "select" statements, including this one: p6spy - 08:59:30|1|1|statement||SELECT ID FROM TAXES WHERE 1 = 0 p6spy - 08:59:30|0|1|statement||SELECT VERSION FROM TAXES WHERE 1 = 0 p6spy - 08:59:30|0|1|statement||SELECT LOCATION FROM TAXES WHERE 1