Christian Beikov (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HHH-15612 (
https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiNTBiZD...
)
Re: Bad SQL generation when using entity graph with ON clause on query (
https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiNTBiZD...
)
When I create a subgraph on an attribute with the ON clause, the SQL join
is duplicated, in the next example the table orderPosition is duplicated.
This is on purpose. Hibernate 5 did the wrong thing here and reused the SQL join for a
fetch, even though it was not safe to do so, because of the ON predicate.
If you want to filter the elements of a fetched collection, you will have to use a
filter.
Closing this issue as rejected.
(
https://hibernate.atlassian.net/browse/HHH-15612#add-comment?atlOrigin=ey...
) Add Comment (
https://hibernate.atlassian.net/browse/HHH-15612#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#100217- sha1:2199b34 )