Migration Guide 3.37

Table of Contents

• Panache Next → Quarkus Data ⚙️ ✅
• Hibernate ORM
  • Upgrade to Hibernate ORM 7.4
  • Behavioral changes
  • DDL changes
  • Minimum database versions
• Hibernate Reactive
  • Upgrade to Hibernate Reactive 3.4
• Hibernate Search
  • Upgrade to Hibernate Search 8.4
• Dev Services
  • Database Dev Services
• Elasticsearch and OpenSearch Dev Services
• ArC
  • Interceptor bindings on default interface methods

Note	We highly recommend the use of quarkus update to update to a new version of Quarkus. Items marked below with ⚙️ ✅ are automatically handled by quarkus update.

Panache Next → Quarkus Data ⚙️ ✅

Panache Next was renamed to Quarkus Data.

Update your dependencies accordingly:

• quarkus-hibernate-panache-next → quarkus-data-hibernate

• quarkus-hibernate-panache-next-deployment → quarkus-data-hibernate-deployment

• quarkus-hibernate-panache-next-parent → quarkus-data-hibernate-parent

Hibernate ORM

Upgrade to Hibernate ORM 7.4

The Quarkus extension for Hibernate ORM was upgraded to Hibernate ORM 7.4.

Hibernate ORM 7.4 includes several behavioral changes. Below are the ones most likely to affect existing applications.

Refer to the Hibernate ORM 7.4 migration guide for more information.

Behavioral changes

• HQL current date and local date on Oracle now translate to trunc(current_date), zeroing out the time part.

• MySQL no longer has a dialect-specific default for hibernate.max_fetch_depth. Applications relying on the implicit default of 2 should set it explicitly.

• Eager @Any associations are now join-fetched by default when loading by id, instead of using a separate SELECT.

• When pagination or a limit is used with a query that fetches a collection, the limit is now processed as part of the SQL query. Use the query hint org.hibernate.limitInMemory to recover the previous behavior.

• Schema actions (including import.sql execution) are now processed even when no @Entity classes are mapped. Applications with an accidental import.sql on the classpath may see it executed.

• SpannerPostgreSQLDialect moved from hibernate-community-dialects (org.hibernate.community.dialect) to hibernate-core (org.hibernate.dialect). Update dialect configuration if using it explicitly.

DDL changes

• A unique constraint is now added to @ElementCollection set tables where appropriate.

• @CreationTimestamp and @UpdateTimestamp columns now have a NOT NULL constraint added automatically.

Minimum database versions

• PostgreSQL: bumped minimum version from 13 to 14

See here for details on the current minimum versions.

Hibernate Reactive

Upgrade to Hibernate Reactive 3.4

The Quarkus extension for Hibernate Reactive was upgraded to Hibernate Reactive 3.4.0.Final

Hibernate Reactive 3.4.0.Final is backwards-compatible with Hibernate Reactive 3.3, with the exception of a few breaking changes inherited from Hibernate ORM and listed above.

Hibernate Search

Upgrade to Hibernate Search 8.4

The Quarkus extensions for Hibernate Search were upgraded to Hibernate Search 8.4.

Hibernate Search 8.4 is fully backwards-compatible with 8.3: no reindexing, schema updates, or code changes are necessary.

Refer to the Hibernate Search 8.4 migration guide for more information.

Dev Services

Database Dev Services

The PostgreSQL Dev Services now default to using a postgis image when hibernate-spatial is in the classpath, or a pgvector image when hibernate-vector is in the classpath. See this section of the documentation for more information.

If this doesn’t match your requirements, make sure to configure the Dev Services image explicitly with quarkus.datasource.devservices.image-name/quarkus.datasource."datasource-name".devservices.image-name.

Elasticsearch and OpenSearch Dev Services

The Elasticsearch Dev Services now default to starting Elasticsearch 9.4, instead of 9.3 previously.

The OpenSearch Dev Services now default to starting OpenSearch 3.6, instead of 3.5 previously.

ArC

Interceptor bindings on default interface methods

Method-level interceptor bindings declared directly on default interface methods are now applied. Previously, only class-level interceptor bindings were applied to default methods; method-level bindings (e.g. @Transactional) were silently ignored.

If you have a method-level interceptor binding on a default interface method that you do not want to be intercepted, remove the binding annotation from the default method.