anchor.diff:  then add the relevant configuration properties in `{config-file}`.
   
   [source,properties]
  ---
  -# configure your datasource
  +.Example `{config-file}`
  +--
  +# datasource configuration
   quarkus.datasource.url = jdbc:postgresql://localhost:5432/hibernate_db
   quarkus.datasource.driver = org.postgresql.Driver
   quarkus.datasource.username = hibernate
  
positive.code: or if you want to reproduce a bug that is based on specific database entries.
  `update` is a best effort from Hibernate ORM and will fail in specific situations
  including altering your database structure which could lead to data loss.
  For example if you change structures related to the foreign key, Hibernate ORM might have to bail out.
  But for development, these limitations are acceptable.
  
  The third approach is to use `quarkus.hibernate-orm.database.generation=none`.
  This approach is best when you are working on a copy of the production data but want to fully control the schema evolution.
  Or if you use a database schema migration tool like https://quarkus.io/guides/flyway[Flyway].
  When you make a change to an entity, make sure to adapt the database schema accordingly.
  
  WARNING: Do not use `quarkus.hibernate-orm.database.generation` `drop-and-create` and `update` in your production environment. You have been warned :)
  
  
  It becomes really powerful when combined with Quarkus configuration profiles.
  You can define different https://quarkus.io/guides/config#configuration-profiles[configuration profiles]
  to select different behaviors depending on your environment.
  This is great because you can define different combinations of Hibernate ORM properties matching the development style you currently need.
  
negative.code: }
  --
  
  To load some SQL statements when Hibernate ORM starts, add an `import.sql` in the root of your resources directory.
  Such a script can contain any SQL DML statements; make sure to terminate each statement with a semicolon.
  This is useful to have a data set ready for your tests or demos.
  
  WARNING: Make sure to wrap methods modifying your database (e.g. `entity.persist()`) within a transaction. Marking a
  CDI bean method `@Transactional` will do that for you and make that method a transaction boundary. We recommend doing
  so at your application entry point boundaries like your REST endpoint controllers.
  
  [[hibernate-configuration-properties]]
  === Hibernate ORM configuration properties
  
  There are various optional properties useful to refine your `EntityManagerFactory` or guide guesses of Quarkus.
  
  There are no required properties, as long as a default datasource is configured.
  
  When no property is set, Quarkus can typically infer everything it needs to setup Hibernate ORM
  and will have it use the default datasource.
  
  The configuration properties listed here allow you to override such defaults, and customize and tune various aspects.
  
  include::{generated-dir}/config/quarkus-hibernate-orm.adoc[opts=optional, leveloffset=+2]
  
  