[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718?page=c...
]
Morten Andersen-Gott commented on HHH-1718:
-------------------------------------------
"Violation of what spec? I am always so amazed we passed the TCK with all these
"spec violations" floating around :) "
Aaah! A Hibernate team classic. It is these types of helpful comments that Hibernate users
and issue reporters have grown so accustomed too. It is what makes using Hibernate such a
joy, compared to professional open source, such as Spring!!
"We passed the TCK, ergo; we are spec compliant. QED" The spec is the written
document, not the test. It is unlikely that the TCK will be able to cover every aspect of
the spec, and this is obviously the case with JPA.
Have multiple bag fetches revert to subselect fetching for all but
one of the bags
----------------------------------------------------------------------------------
Key: HHH-1718
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718
Project: Hibernate3
Issue Type: Improvement
Components: core, query-criteria, query-hql
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: hql+collection
Attachments: hibernate_eksempel.zip
Follow on to HHH-1413. Multiple bag fetches were simply disallowed as the resolution to
that particular case in the interest of working around that issue.
The correct longer term solution is to not fetch all the bags at once, ideally reverting
to subselect fetching for all but one of the bags.
--
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