[hibernate-issues] [JIRA] (HHH-16927) Some NUMBER column types now get mapped to Boolean/Integer/Long instead of BigDecimal

Morgan PEYRE ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGM5NmU0ZDcw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16927?atlOrigin=eyJpIjoiNGM5Nm... ) HHH-16927 ( https://hibernate.atlassian.net/browse/HHH-16927?atlOrigin=eyJpIjoiNGM5Nm... ) Some NUMBER column types now get mapped to Boolean/Integer/Long instead of BigDecimal ( https://hibernate.atlassian.net/browse/HHH-16927?atlOrigin=eyJpIjoiNGM5Nm... ) Issue Type: Bug Affects Versions: 6.2.2, 6.2.4, 6.2.5, 6.2.6 Assignee: Unassigned Components: hibernate-core Created: 12/Jul/2023 04:10 AM Environment: Hibernate 6.2.5.Final Oracle XE 18 (Docker image gvenzl/oracle-xe:18-slim-faststart) Java 17.0.7 (OpenJDK 17.0.7+7-Ubuntu-0ubuntu122.04.2) Ubuntu Ubuntu 22.04.2 / WSL2 (GNU/Linux 5.15.90.1-microsoft-standard-WSL2 x86_64) Priority: Major Reporter: Morgan PEYRE ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) It seems that some type mappings have changed between Hibernate versions 5 and 6, is this intentional ? Here are some of the changes I’ve noticed: *SQL Data type* *Java type (Hibernate 5)* *Java type (Hibernate 6)* NUMBER(19,0) java.math.BigDecimal java.lang.Long NUMBER(1,0) java.math.BigDecimal java.lang.Integer or java.lang.Boolean ( https://hibernate.atlassian.net/browse/HHH-16927#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16927#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#100231- sha1:2d13be9 )