Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16955 ( https://hibernate.atlassian.net/browse/HHH-16955?atlOrigin=eyJpIjoiMjg0OW... ) Re: Improve resolution of implicit Query select clauses ( https://hibernate.atlassian.net/browse/HHH-16955?atlOrigin=eyJpIjoiMjg0OW... ) In cases where we have no select clause associated with the query, Hibernate sometimes chooses the “wrong” interpretation. I say “wrong” because it was not completely defined before and a few of the well-defined cases had bugs. * If the requested return is an array ( Object[].class e.g.), we will return all roots as well as all non-fetched joins * Otherwise, only the single root is returned. It is an error for such a query to have multiple roots (cross joins should probably be included here as well, but are not at the moment) ( https://hibernate.atlassian.net/browse/HHH-16955#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16955#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#100232- sha1:304e1c7 )