Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

HHH-15175 - Remove support for database versions that are unsupported by vendors 6.2 edition

This commit is contained in:
Jan Schatteman 2022-10-31 23:11:53 +01:00 committed by Christian Beikov
parent a471bbea8c
commit 9d62179d40
1 changed files with 51 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
migration-guide.adoc
View File

@ -37,4 +37,54 @@ To retain backwards compatibility, configure the setting `hibernate.type.preferr
Previously, since Hibernate 6.0, columns of type `number` with scale 0 on Oracle were interpreted as `boolean`, `tinyint`, `smallint`, `int`, or `bigint`,
depending on the precision.
Now, columns of type `number` with scale 0 are interpreted as `int` or `bigint` depending on the precision.
Now, columns of type `number` with scale 0 are interpreted as `int` or `bigint` depending on the precision.
=== Removal of support for legacy database versions
This version introduces the concept of minimum supported database version for most of the database dialects that Hibernate supports. This implies that the legacy code for versions that are no longer supported by their vendors, has been removed from the hibernate-core module. It is, however, still available in the hibernate-community-dialects module.
The minimum supported dialect versions are as follows:
|===
|Dialect |Minimum supported version
|MySQL
|5.7
|SQL Server 2008
|10.0
|DB2
|10.5
|DB2i
|7.1
|DB2z
|12.1
|MariaDB
|10.3
|H2
|1.4.197
|Derby
|10.14.2
|Sybase
|16.0
|CockroachDB
|21.1
|PostgreSQL
|10.0
|Oracle
|11.2
|HSQLDB
|2.6.1
|===