Package io.quarkus.hibernate.orm.runtime

Interface HibernateOrmRuntimeConfigPersistenceUnit.HibernateOrmConfigPersistenceUnitDatabaseGeneration

Enclosing interface:
HibernateOrmRuntimeConfigPersistenceUnit
@Deprecated(forRemoval=true, since="3.22") public static interface HibernateOrmRuntimeConfigPersistenceUnit.HibernateOrmConfigPersistenceUnitDatabaseGeneration
Deprecated, for removal: This API element is subject to removal in a future version.

  • Method Details

    • generation

      @WithParentName @Deprecated(forRemoval=true, since="3.22") Optional<@WithConverter(io.quarkus.runtime.configuration.TrimmedStringConverter.class) String> generation()
      Deprecated, for removal: This API element is subject to removal in a future version.
      Select whether the database schema is generated or not. `drop-and-create` is awesome in development mode. This defaults to 'none', however if Dev Services is in use and no other extensions that manage the schema are present this will default to 'drop-and-create'. Accepted values: `none`, `create`, `drop-and-create`, `drop`, `update`, `validate`.

    • createSchemas

      @Deprecated(forRemoval=true, since="3.22") Optional<Boolean> createSchemas()
      Deprecated, for removal: This API element is subject to removal in a future version.
      If Hibernate ORM should create the schemas automatically (for databases supporting them).

    • haltOnError

      @Deprecated(forRemoval=true, since="3.22") Optional<Boolean> haltOnError()
      Deprecated, for removal: This API element is subject to removal in a future version.
      Whether we should stop on the first error when applying the schema.