Hibernate version:
2.1.7

Name and version of the database you are using:
MySQL 4.0
MSSQL 2000

Hello everyone,

When mapping a column/table which name is a reserved keyword (of the database server), you have to use escapes like '' (MySQL) or [] (MSSQL) in the mapping descriptors (e.g. column="[index]").

Unfortunately, these escape characters are dependant on the database server. Is there any way to stay database independant and let the Dialect do the escaping?

Regards,

Andreas

use backticks in the mapping file

Thanks for your help.

I think this only solves part of the problem. How should I know which names are reserved keywords (those are database server dependant, are they?)? I would need to escape each table/column name in the descriptor just to be on the safe side. Couldn't this be done by some Hibernate configuration?

Regards,

Andreas

Yes, escape everything. There is currently no option to do this automatically.

one could use a NamingStrategy for this i presume ,)

it could just quote whatever is not quoted.

Hmm, good idea yes ... I should read my own blog articles more often :)

It is a bad advice.
I use hbm2java to generate my pogo, now you see that it simply produce :

I think that implementation for a specific database should escape fields if needed.

I am using Hibernate3 with MySQL, but in Hibernate2 it was all right, fields has been escaped.

it only produces that if you put quotes in your property name which you should never do. the quotes goes in the column name!

-max

I define only property names to ensure that DB colum mapped to a property with a same name.
When you have a few developers someone will misspell property name and instead of `center` I will get `centre`.

B.t.w. does this issue has been reported in JIRA, I can't find anything related there ?

did you read the thread and tried to use namingstrategy to apply quoting transparently ?

Yes, I read the thread, this why I am posting here.
I am not using NamingStrategy.
If I would try to do some tricks and default implementation wouldn't allow me to do so, I would use NamingStrategy to find my way.
But I am talking about an obvious bug in MySQL dialect.
A simple generated SQL won't work :

My conclusion is that MySQL dialect implementation should escape field names, to comply with:
http://dev.mysql.com/doc/mysql/en/reserved-words.html

i don't understand ?!

If NamingStrategy can solve your problem why don't you use it ?

You can implement a NamingStrategy that obeys the url you just posted.

Newer mind, users who find this topic will figure out that you can't rely on implementation provided.

huh ? we explicit state that quoting is the job for the user.

And if you think about it and investigate a bit you will see its almost impossible to make this work in the dialect since databases has different reserved keywords and different need/semantics for quoting....

Oh yes, before posting here, I check the source and how other people solve the problem.

But I can't see why MySQL dialect can't take care for reserved words that specific to MySQL database ?