A dialect is a class that provides information about the specifics of a database and translators for the SQL dialect of the database.

Hibernate ORM supports a wide range of dialects out of the box.

Usually, Hibernate supports at least the database version that is also still supported by the respective vendor.In many cases though, Hibernate supports even older versions of the databases,but the support for these versions is not guaranteed.

Below is a list of supported dialects and the minimum required version of the database.

Third-parties publish additional dialects for Hibernate ORM, providing their own support for more databases, or extended support beyond what is built in Hibernate ORM.

These dialects are not directly supported by the Hibernate team:

• The Hibernate ORM CI does not run any test against these dialects, the dialect’s authors have their own test suite.

• The Hibernate team will not address issues reported against these dialect, but the dialect’s authors have their own issue tracker.

Below is a list of third-party dialects with links to relevant websites.

Community dialects are not included inorg.hibernate.orm:hibernate-core and require an additional dependency toorg.hibernate.orm:hibernate-community-dialects.

These dialects are not directly supported by the Hibernate team:

• The Hibernate ORM CI does not run any test against these dialects.

• The Hibernate team will not address issues reported against these dialect.

Instead, the dialects are maintained on a best-effort basis by vendors or individuals.

Below is a list of community dialects and the minimum required version of the database.

If a database vendor wants their database dialect to be included in thehibernate-core artifact,several requirements have to be fulfilled:

• The vendor must provide access to a dedicated database server that can be used for testing

• The vendor must provide contact details to at least one employee who is mainly responsible for the maintenance of the dialect

• The responsible employee of the vendor must actively monitor and react to failures of the testsuite against the respective database

• The responsible employee of the vendor must ensure the testsuite is configured correctly in order for it to succeed on the respective database

• If the responsible employee of the vendor leaves the company, the vendor must provide contact details to a new responsible employee

In case the responsible employee is unreachable for a longer period or issues with the dialect are not attended to in a timely manner,the Hibernate team will move the dialect back to thehibernate-community-dialects artifact.

The requirements for the database server are:

• JDK 17 installed

• Git installed

• Access to the database through non-confidential credentials

• Access via SSH through confidential credentials

Get in touch with the Hibernate team onZulipif you want to request the move of your dialect to hibernate-core.