[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3394?page=c...
]
Thomas Scherm commented on HHH-3394:
------------------------------------
I suggest to change the priority to critical. When designing strong componized systems the
creation of data provider is usefull. Doing batch processing, i.e. for invoive processing
using ScrollableResults and prefetching is a nice and high performing solution.
In lack of predictability of this bug, intensive testing and debugging is required or a
doing as serious tradeoff in performance, falling back to lazy loading.
ScrollableResults delivers sometime wrong collections when used with
a LEFT JOIN FETCH clause
---------------------------------------------------------------------------------------------
Key: HHH-3394
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3394
Project: Hibernate Core
Issue Type: Bug
Components: query-hql
Affects Versions: 3.2.6
Environment: Windows, Java SE 6.06, Oracle 9 / 10, Hibernate 3.2.6
Reporter: Thomas Scherm
Following stament is used to create a ScrollableResult from a Query.
SELECT DISTINCT f FROM Fall f
LEFT JOIN FETCH f.leistungen l
WHERE (f.status = '2' OR f.status = '3') AND f.quartalJahr = ?
It schould deliver a Faelle with prefeched sets of Leistungen.
The first row is ok. All subsequent rows return exactly one leistungen.
Th SQL Statement is ok, the session cache works fine and has the missing Leistungen, but
they are not attached.
As Workaround we removed the FETC clause and let it work with lazy loading. It works.
--
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