anchor.diff:  your entity changes or any change to your `import.sql` is immediately picked up and the schema updated without restarting the application!
   
   [TIP]
  ---
  +====
   By default in `dev` and `test` modes, Hibernate ORM, upon boot, will read and execute the SQL statements in the `/import.sql` file (if present).
   You can change the file name by changing the property `quarkus.hibernate-orm.sql-load-script` in `application.properties`.
  ---
  +====
   
   The second approach is to use `quarkus.hibernate-orm.database.generation=update`.
   This approach is best when you do many entity changes but
  
positive.code: To cache a query, mark it as cacheable on the `Query` instance:
  
  [source,java]
  --
  Query query = ...
  query.setHint("org.hibernate.cacheable", Boolean.TRUE);
  --
  
  If you have a `NamedQuery` then you can enable caching directly on its definition, which will usually be on an entity:
  
  [source,java]
  --
  @Entity
  @NamedQuery(name = "Fruits.findAll",
        query = "SELECT f FROM Fruit f ORDER BY f.name",
        hints = @QueryHint(name = "org.hibernate.cacheable", value = "true") )
  public class Fruit {
     ...
  --
  
  That's all! Caching technology is already integrated and enabled by default in Quarkus, so it's enough to set which ones are safe to be cached.
  
  
negative.code: [NOTE]
  ====
  The double quotes are mandatory if your region name contains a dot. For instance:
  
  [source,properties]
  ----
  quarkus.hibernate-orm.cache."org.acme.MyEntity".memory.object-count=1000
  ----
  ====
  
  
  