Hibernate Core version: 3.2.1 GA
I had a tutorial-like setup which worked fine in a PostgreSQL environment, but when I changed the hibernate.cfg.xml to use MySQL instead, the automatic creation of one table failed. Copy'n'pasting the debug SQL query output into a mysql console session revealed that it was the column name "lock" it was unhappy with. Changing the name in the mapping file (and get/setters in source file) solved the problem.
I bet this kind of behavior isn't something the Hibernate user should need to worry about, and that Hibernate is supposed to dodge "reserved name"-collisions, e.g. by changing the name to "lock_" or something?
|