Uploaded image for project: 'Quarkus Documentation'
  1. Quarkus Documentation
  2. QDOCS-1325

[New Feature]: Offline startup and dialect configuration for Hibernate ORM

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      :_mod-docs-content-type: REFERENCE
      [id="ref_rn-qdocs-1325-hibernate-orm-offline-startup-dialect-config_{context}"]
      = Hibernate ORM offline startup and dialect configuration

      In {ProductLongName} {ProductVersion}, Hibernate ORM can start offline without connecting to the database.
      Hibernate ORM still provides sensible defaults for dialect and version, so explicit configuration is only needed in edge cases where the database setup differs from common defaults.
      The database must still be available before the application can persist or query data.

      This new capability allows applying _dialect-specific_ settings at startup when necessary.
      In environments where a live database is unavailable on startup, this feature avoids unactionable warnings and allows build-time configuration of runtime dialect behavior to match the targeted database version and configuration.

      For the relevant _dialect-specific_ settings, see the link:https://quarkus.io/guides/hibernate-orm#hibernate-configuration-properties[Hibernate ORM configuration properties] and search for `quarkus.hibernate-orm.dialect.`

      For more details, see the related resources:

      * link:https://github.com/quarkusio/quarkus/pull/49408[GitHub Pull Request #49408]
      * link:https://quarkus.io/blog/quarkus-3-26-released/#hibernate[Quarkus 3.26 release blog – Hibernate section]

      // https://issues.redhat.com/browse/QDOCS-1325
      // SME: Yoann Rodière
      // Data
      // New feature
      // include::rn/ref_rn-qdocs-1325-hibernate-orm-offline-startup-dialect-config.adoc[leveloffset=+2]
      Show
      :_mod-docs-content-type: REFERENCE [id="ref_rn-qdocs-1325-hibernate-orm-offline-startup-dialect-config_{context}"] = Hibernate ORM offline startup and dialect configuration In {ProductLongName} {ProductVersion}, Hibernate ORM can start offline without connecting to the database. Hibernate ORM still provides sensible defaults for dialect and version, so explicit configuration is only needed in edge cases where the database setup differs from common defaults. The database must still be available before the application can persist or query data. This new capability allows applying _dialect-specific_ settings at startup when necessary. In environments where a live database is unavailable on startup, this feature avoids unactionable warnings and allows build-time configuration of runtime dialect behavior to match the targeted database version and configuration. For the relevant _dialect-specific_ settings, see the link: https://quarkus.io/guides/hibernate-orm#hibernate-configuration-properties [Hibernate ORM configuration properties] and search for `quarkus.hibernate-orm.dialect.` For more details, see the related resources: * link: https://github.com/quarkusio/quarkus/pull/49408 [GitHub Pull Request #49408] * link: https://quarkus.io/blog/quarkus-3-26-released/#hibernate [Quarkus 3.26 release blog – Hibernate section] // https://issues.redhat.com/browse/QDOCS-1325 // SME: Yoann Rodière // Data // New feature // include::rn/ref_rn-qdocs-1325-hibernate-orm-offline-startup-dialect-config.adoc[leveloffset=+2]

      Affected version: 3.26

      SME: rh-ee-yrodiere 

      Resources:

      Note: May end up as a Tech Preview depending on testing results

              mmaler@redhat.com Michal Maléř
              shjones@redhat.com Sheila Jones
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: