[hibernate-issues] [JIRA] (HHH-15454) Primitive type returned by metamodel in combination with tuple query leads to exceptions

Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjMyZWJmNzc1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNjMyZW... ) HHH-15454 ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNjMyZW... ) Primitive type returned by metamodel in combination with tuple query leads to exceptions ( https://hibernate.atlassian.net/browse/HHH-15454?atlOrigin=eyJpIjoiNjMyZW... ) Change By: Tassilo Karge ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f50ce4... ) The function getJavaType() on Attribute returns the type of the field it represents in the entity. This may be a primitive type. However, that leads to inconsistencies, for example when selecting that attribute in a tuple query. See the related test case for an example. Reading Judging from the title, changes in this issue might have been fixed on the master by the following PR : ; [https://github.com/hibernate/hibernate-orm/pull/4784|https://github.com/h...] If that is the case metamodel is intended to return primitive types. Therefore , it just the tuple is what needs to be backported to the current 5 fixed. x version. ( https://hibernate.atlassian.net/browse/HHH-15454#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15454#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#100205- sha1:6417f3f )