[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-4982) JPA OneToOne(optional=true) not supported with @PrimaryKeyJoinColumn
Gail Badner (JIRA)
noreply at atlassian.com
Wed Oct 12 07:04:20 EDT 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gail Badner resolved HHH-4982.
------------------------------
Resolution: Fixed
> JPA OneToOne(optional=true) not supported with @PrimaryKeyJoinColumn
> --------------------------------------------------------------------
>
> Key: HHH-4982
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4982
> Project: Hibernate Core
> Issue Type: Bug
> Affects Versions: 3.5.5
> Environment: Hibernate 3.3.1, annotations 3.4.0, MsSQL DB.
> Reporter: Bruno Melloni
> Assignee: Gail Badner
> Labels: jpa2
> Fix For: 3.6.8, 4.0.0.next
>
>
> Rejected issue ANN-725 covers this partially. I might have misunderstood, but it seems the reason for rejecting is that @NotFound provides the same capability.
> All information I could find for JPA and other ORM tools indicates that this capability is supplied by @OneToOne(optional=true). Hibernate seems to be the lone ORM tool that requires the use of a proprietary annotation: @NotFound.
> @NotFound works, but the problem is that it makes the application no longer be pure-JPA. Not supporting pure-JPA outer joins would seem to be a major bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list