anchor.diff:             -p 5432:5432 postgres:10.5
   --
   
  +This will start a non-durable empty database: ideal for a quick experiment!
   ====
   
   == Setting up and configuring Hibernate ORM with a `persistence.xml`
   
  -Alternatively, you can set a `META-INF/persistence.xml` to setup Hibernate ORM.
  +Alternatively, you can use a `META-INF/persistence.xml` to setup Hibernate ORM.
   This is useful for:
   
   * migrating existing code
  
positive.code: difference is that you would specify your Hibernate ORM configuration in `META-INF/persistence.xml`:
  
  [source,xml]
  --
  <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  
negative.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 which violate a foreign key constraint, 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].
  
  With this approach when making changes to an entity, make sure to adapt the database schema accordingly;
  you could also use `validate` to have Hibernate verify the schema matches its expectations.
  
  WARNING: Do not use `quarkus.hibernate-orm.database.generation` `drop-and-create` and `update` in your production environment.
  
  
  These approaches become 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.
  