A new topic, 'H2 database regression 1.9.5 -> 2.0-rc5', has been made on a
board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=661.new#new
The text of the topic is shown below:
I moved a bunch of changelog files and associated machinery to 2.0-rc5. Oddly,
my unit tests began failing. I turned the H2 trace level up, and saw
that--this is my best guess--Liquibase's H2 database implementation is trying
to be nice about keywords. I had a column named "value" in one of my tables.
H2 is reporting that Liquibase is issuing the command:
CREATE TABLE NameType (code VARCHAR(30) NOT NULL, "value" VARCHAR(100),
CONSTRAINT PK_NAMETYPE PRIMARY KEY (code))
Note the quotes around value, which is a keyword in H2. This quoting, which I
THINK is new, has the other effect of case-sensitizing the column.
Consequently, an insert statement, later on down the line, produced by
Hibernate, fails, because the VALUE column cannot be found.
This is, I guess, my fault (for unwittingly using a keyword as a column name),
but offhand I'm not sure how to either (a) tell Liquibase to stop being helpful
or (b) quote ALL my identifiers in my changelog. Should I, for example,
declare it like this:
column name=""value""
...in my column tag?
Thanks,
Laird
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
