Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *updated* an issue
Hibernate ORM (
https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNzkxZjg4Nzcz...
) / Bug (
https://hibernate.atlassian.net/browse/HHH-14124?atlOrigin=eyJpIjoiNzkxZj...
) HHH-14124 (
https://hibernate.atlassian.net/browse/HHH-14124?atlOrigin=eyJpIjoiNzkxZj...
) Entity graph (fetch graph) is incorrectly applied to query results beyond the first one
(
https://hibernate.atlassian.net/browse/HHH-14124?atlOrigin=eyJpIjoiNzkxZj...
)
Change By: Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
)
When I apply a fetch graph to a query, it is correctly applied to the first result: eager
associations that are not mentioned in the fetch graph are overridden and made lazy.
However, this is not true for query results beyond the first one (index 1, 2, etc.): for
those results, eager associations are loaded eagerly, even if they are not mentioned in
the fetch graph.
This used to work in 5.4.18.Final.
PR coming, with a test case and hopefully a fix.
(
https://hibernate.atlassian.net/browse/HHH-14124#add-comment?atlOrigin=ey...
) Add Comment (
https://hibernate.atlassian.net/browse/HHH-14124#add-comment?atlOrigin=ey...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100140- sha1:42b370d )