]
Gail Badner resolved HHH-5749.
------------------------------
Assignee: Gail Badner
Resolution: Rejected
See
.
In particular, it says:
"implicit join result in inner joins in the resulting SQL statement."
ORDER BY with many-to-one association doesn't make an outer join
with flag : nullable = true
--------------------------------------------------------------------------------------------
Key: HHH-5749
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5749
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.0
Reporter: ghanassia
Assignee: Gail Badner
I would like to react to the following post :
https://forum.hibernate.org/viewtopic.php?f=1&t=949719&view=next
Bernard Ligny is right by expected this behiavour :
Extract of topic :
" But this leads me to the following suggestion:
I was wondering if, with the help of the not-null attribute in my <many-to-one>
mapping, Hibernate could not smartly utilize such information in order to decide how to
translate the implicit join:
- if not-null="true" => translated into a normal join
- if not-null="false" => translated into an outer join "
I think than hibernate will better with this behiavour, for me this is bug to ignore the
not-null information in association many-to-one to build SQL request.
Of course is possible to write explictly the outer join, but is it realy the philosophy
of hibernate ?
Best regards,
Cédric Ghanassia
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: