[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-476?page=co...
]
Benjamin Bentmann commented on ANN-476:
---------------------------------------
Oracle at least treats identifiers as case sensitive when quoted and
case insensitive when unquoted.
Oh, I see, thanks for your info. Then it might be a reasonable default behavior, to simply
leave the compounded table/column name without quotes. If the resulting name really needs
quoting, the developer can/should explicitly specify the name via metadata and free the
naming strategy from guessing. Besides, there seem to be far less reserved SQL keywords
with an underscore in their name than others so I suppose the need to quote the compounded
name due to conflicts is quite rare.
EJB3 naming strategy struggles with quoted identifiers when
generating composed table/column names
--------------------------------------------------------------------------------------------------
Key: ANN-476
URL:
http://opensource.atlassian.com/projects/hibernate/browse/ANN-476
Project: Hibernate Annotations
Type: Improvement
Versions: 3.2.0.ga
Environment: Hibernate Core/Annotations v3.2.0.GA
JDK 1.5.0_07
Reporter: Benjamin Bentmann
Priority: Minor
Fix For: 3.2.1
Improve EJB3 naming strategy to allow quoted identifiers when composing default
table/column names.
Related forum posting:
http://forum.hibernate.org/viewtopic.php?t=966257
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira