Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15612 ( https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiMjI1NG... ) Re: Bad SQL generation when using entity graph with ON clause on query ( https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiMjI1NG... ) Note that the additional join in your case is added because the explicit join in your query can not be reused for fetching of the association. This is because you use a custom ON clause. Note that it would not be safe to use the data from that SQL join because if you change the collection, Hibernate might remove rows which were previously filtered out through your condition. ( 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#100209- sha1:5f5cf47 )