[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2492?page=c...
]
Manoj Pallikkattil commented on HHH-2492:
-----------------------------------------
Steve, I understand this is probably a bad database design. But it is going to be a very
huge effort for us to fix the database design to make it work. We have more than 10
production clients with most of them having 10gig database sizes. If I would start off
with a new database design I probably will not do this again. Only reason I am pursuing
this is because I am using an existing database and I want to use hibernate. Let me ask
you this, how big of an effort is it for hibernate to enable autogeneration for non
primary key columns ? If you say it is going to be a huge one then I am ok with not
pursuing it. But if this a matter of few hours or a day, it might be worth it since other
people are experiencing similar issues. And with this feature enabled hibernate will only
be able to support more datababase schemas. So it is not a bad thing. Well just my 2
cents. Thanks.
Also as per your comments above about using properties tag, I was able to make hibernate
use my sequence column as primary key and my guid column as a unique key using the
properties tag and use this key to join other tables. The issue with this one is that I
cannot enable schema verification since the PK's are reversed in hibernate.
Enable <generator> tag for non primary key columns that are
autogenerated or is an identity
-------------------------------------------------------------------------------------------
Key: HHH-2492
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2492
Project: Hibernate3
Issue Type: New Feature
Affects Versions: 3.2.2
Environment: 3.2.2, Oracle 9i, SQL Server 2000
Reporter: Manoj Pallikkattil
Currently hibenate allow <generator> tag for primary keys, i.e inside the
<id> tag. It would be good if we can use the generator tag for non primary key
columns also. Our current datamodel has a UUID char 32 as the primary key and ID column
which is a sequence for Oracle and an Identity for SQL Server is a unique key. I could get
this to work with Oracle using Parameterized User Type but I have not been able to achieve
this for SQL Server since the identity column is filled on the insert. If we could use the
<generator> tag inside a <property> tag this would resolve this issue.
--
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