Wilber Saca ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15612 ( https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiMzU0Nz... ) Re: Bad SQL generation when using entity graph with ON clause on query ( https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiMzU0Nz... ) I’m not getting duplicate elements, my problem is the deleted elements are not filtered due to the new JOIN added by the entity graph. It’s worse if I add a combination of ORDER BY + DISTINCT to the same query, in that case I receive a database exception ORA-01791: not a SELECTed expression ( http://oraclequirks.blogspot.com/2009/04/ora-01791-not-selected-expressio... ) because the query JOIN is replaced by the entity graph JOIN in the SELECTed results and they are not used to declare the order in the original query. On internet there are solutions similar to mine https://stackoverflow.com/a/65703150/1432916 ( https://stackoverflow.com/a/65703150/1432916 ) , does this means with Hibernate 6 we can’t use LEFT JOIN + ON with entity graph to fetch data? I have used Blaze before and would be a good option, but now I’m trying to migrate a project to Jakarta 10 making as few changes as possible. ( 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:392b984 )