Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZDA2YTUxNjVl... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15464?atlOrigin=eyJpIjoiZDA2YT... ) HHH-15464 ( https://hibernate.atlassian.net/browse/HHH-15464?atlOrigin=eyJpIjoiZDA2YT... ) Allow JdbcType to expose the type code to use for DDL ( https://hibernate.atlassian.net/browse/HHH-15464?atlOrigin=eyJpIjoiZDA2YT... ) Issue Type: Improvement Assignee: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-core Created: 25/Aug/2022 07:35 AM Fix Versions: 6.1.3 Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Usually, the JdbcType#getJdbcTypeCode is only used for binding null and all other code that wants to know the “type” of a JdbcType will use getDefaultSqlTypeCode. When emulating certain types like JSON through a CLOB on databases that do not have a native JSON type, the “logical type” and DDL type will differ. For some code it is important to understand that the DDL type of something is a CLOB though, so it is desirable to query the DDL type separately. My proposal is to add a new method {{default int getDdlTypeCode() { return getDefaultSqlTypeCode(); } }} and override this method for JdbcType implementations that do such an emulation. ( https://hibernate.atlassian.net/browse/HHH-15464#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15464#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#100206- sha1:9fe2ddf )