[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-947) Allow nullable columns in a composite-id

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole closed HHH-947.
------------------------------


Closing stale resolved issues

> Allow nullable columns in a composite-id
> ----------------------------------------
>
>                 Key: HHH-947
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-947
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: core
>         Environment: Hibernate 3.0.5, Oracle 9.2
>            Reporter: Patrick Higgins
>
> We have some tables that don't have a primary key, but do have a unique index with nullable columns in it. This is a conceptually broken data model, but code maintains the semantics that NULL = NULL which the database does not enforce. Mapping these tables with Hibernate 3 does not work because any record with a NULL value in a composite-id field returns a null in query results. I have not looked at INSERT/UPDATE behavior, but it is likely broken, too.
> It seems that Hibernate should be able to maintain the semantics that NULL = NULL, as well.

-- 
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