[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-2492) Enable <generator> tag for non primary key columns that are autogenerated or is an identity
Steve Ebersole (JIRA)
noreply at atlassian.com
Wed Mar 14 17:43:09 EDT 2007
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2492?page=all ]
Steve Ebersole closed HHH-2492:
-------------------------------
Resolution: Fixed
I'm sorry, but use of an IDENTITY column makes no sense as anything other than a PK. And anyway, if you *really* want to do this, you can via the generated properties values which are covered in the documentation.
> 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
> Type: New Feature
> 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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list