I've recently upgraded to Hibernate 3.5.0-CR-1.

Several of my tables have columns named "order".
It worked before, but now the SQL statement that Hibernate generates is malformed around the word "order", namely it's missing the tablename infront of the column name, as in this example (plus there's an extra empty line):

select
footerlink0_.id as id30_,
footerlink0_.locationId as locationId30_,
footerlink0_.locationLevel as location3_30_,

order as order30_,
footerlink0_.text as text30_,
footerlink0_.type as type30_,
footerlink0_.url as url30_ from
footerLinks footerlink0_
where
footerlink0_.locationLevel=?
and footerlink0_.locationId=?
and footerlink0_.type=?;

The db dialect is MySQL, and the server is (understandably) unhappy with the statement.
I do agree that "order" is not the best name for a database column, but still...

When it was working, Hibernate was generating this statement instead:

select
footerlink0_.id as id30_,
footerlink0_.locationId as locationId30_,
footerlink0_.locationLevel as location3_30_,
footerlink0_.order as order30_,
footerlink0_.text as text30_,
footerlink0_.type as type30_,
footerlink0_.url as url30_
from
footerLinks footerlink0_
where
footerlink0_.locationLevel=?
and footerlink0_.locationId=?
and footerlink0_.type=?

So, any suggestions?
Thanks,
Radu

"order" is a reserved keyword on most databases (except MySQL) therefore I would say that your were lucky that it worked until
now (Hiberante3.3).
In order to fit standard naming conventions I suggest you to change name for those attributes if you intend to use Hiberante3.5.
Otherwise you have to open an issue on hibernate jira (in hope that someone will fix this).

Oracle database:



No mysteries here, you just quote the reserved name. Can't Hibernate do the same?

you can define like this

Thanks, it actually works using the @Column annotation and the quotes.