[hibernate-issues] [JIRA] (HHH-15446) Allow Dialect version to be specified separately from the dialect class name

Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYmFiODZjMmYx... ) / Task ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiYmFiOD... ) HHH-15446 ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiYmFiOD... ) Allow Dialect version to be specified separately from the dialect class name ( https://hibernate.atlassian.net/browse/HHH-15446?atlOrigin=eyJpIjoiYmFiOD... ) Change By: Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We need to be able to specify the dialect version by using the environment settings {{JAKARTA_HBM2DDL_DB_VERSION}}, {{JAKARTA_HBM2DDL_DB_MAJOR_VERSION}}, {{JAKARTA_HBM2DDL_DB_MINOR_VERSION.}} Right now, if the version is specified like this, it is not taken into account. This would allow replacing something such as {{cfg.setProperty( AvailableSettings.DIALECT, Oracle10gDialect.class.getName() );}} with {code:java}cfg.setProperty( AvailableSettings.DIALECT, OracleDialect.class.getName() ); cfg.setProperty( AvailableSettings.JAKARTA_HBM2DDL_DB_MAJOR_VERSION, "10" );{code} NB: once the above is implemented, tests that used these deprecated Dialects, should take special care in assuring that they actually get the requested dialect. (e.g. {{BatchVersionedDataConfigTest }}) ( https://hibernate.atlassian.net/browse/HHH-15446#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15446#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#100204- sha1:2e7ea99 )