From: Ingo J. (JIRA) <no...@at...> - 2006-06-10 18:47:33
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1751?pa= ge=3Dcomments#action_23306 ]=20 Ingo Jobling commented on HHH-1751: ----------------------------------- I am confirming this bug. Until this is fixed, I modified my HQL by removi= ng the fetch join on "one to many" collection (resulting in n+1 selects). This seems to be the same bug as HHH-1283 ScrollableResults JoinFetch don't= set child collection correctly=E3=80=80after the second parent object > Collection corruptly loaded when join fetching and scrolling (org.hiberna= te.impl.FetchingScrollableResultsImpl) > -------------------------------------------------------------------------= -------------------------------------- > > Key: HHH-1751 > URL: http://opensource.atlassian.com/projects/hibernate/browse/H= HH-1751 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr2 > Reporter: Maarten Winkels > Attachments: Child.java, HQLScrollFetchTest.java, Parent.java, ParentChi= ld.hbm.xml, scroll-fetch-collection.patch > > > When scrolling a query that has a jon fetch on a collection (set), the co= llection is not loaded correctly. It appears that only the first item in th= e collection is correctly loaded. > Th attached tests show this behaviour, as well as a number of orderings i= n the query to show how the collection is corruptly loaded. --=20 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= .jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |