anchor.diff:  The team thought it was better to have _some_ caching capability to start with, than having nothing; you can expect better caching solution to be integrated in future releases, and any help and feedback in this area is very welcome.
   
   [NOTE]
  ---
  +====
   These caches are kept locally, so they are not invalidated or updated when changes are made to the persistent store by other applications.
   
   Also, when running multiple copies of the same application (in a cluster, for example on Kubernetes/OpenShift), caches in separate copies of the application aren't synchronized.
  
positive.code: 
  [source]
  .application.properties
  --
  %dev.quarkus.hibernate-orm.database.generation = drop-and-create
  %dev.quarkus.hibernate-orm.sql-load-script = import-dev.sql
  
  
negative.code: * or if you like it the good old way
  
  [NOTE]
  ====
  If you have a `persistence.xml`, then you cannot use the `quarkus.hibernate-orm.*` properties
  and only persistence units defined in `persistence.xml` will be taken into account.
  ====
  
  Your `pom.xml` dependencies as well as your Java code would be identical to the precedent example. The only
  difference is that you would specify your Hibernate ORM configuration in `META-INF/persistence.xml`:
  
  [source,xml]
  .Example persistence.xml resource
  ----
  <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence
  