[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4982?page=c...
]
Gail Badner commented on HHH-4982:
----------------------------------
There is conflicting information here.
Is JPA OneToOne(optional=true) working in general, but broken in particular use cases?
Please try 3.6.0. If you are having a problem with a particular use case, please check to
see if there is already an issue reported for your use case and link this issue to that
one.
JPA OneToOne(optional=true) not supported, supported alternative
NotFound() is hibernate-proprietary!
-----------------------------------------------------------------------------------------------------
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
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.
-
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