[hibernate-issues] [Hibernate-JIRA] Commented: (HB-892) NamingStrategy functionality
[
http://opensource.atlassian.com/projects/hibernate/browse/HB-892?page=com...
]
Geoffrey De Smet commented on HB-892:
-------------------------------------
Is there a similar issue for hibernate3 for this?
I'd like to get rid of the hashhash FK constraints.
NamingStrategy functionality
----------------------------
Key: HB-892
URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-892
Project: Hibernate2
Type: Improvement
Reporter: Prasad Rachakonda
In Hibernate version 2.1.1, We have something called "NamingStrategy" concept,
which allows us to specify "Naming Standards" for database objects. We can
provide rules for automatically generating database identifiers from Java dentifiers or
for processing "logical" columns and table names given in the mapping file into
"physical" table and column names.
Note: This version of Hibernate only supports "tablenames" and "column
names".
It will be helpful if hibernate team can provide the "Naming Strategy support for
other database objects,like.Foreign key constraint etc."
Currently we are planning to use some temp solutions once we get the fix(probably in
future releases), we will be using this feature.
I appreciate your quick response.
--
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