anchor.diff:  }
   ----
   
  +.Content of the +hibernate_sequences+ cache in +CACHE_PER_TABLE+
   [cols="2*", options="header"]
   |===
     ^| KEY
     ^| NEXT VALUE
  -   | [type="TABLE", "name"="hibernate_sequences", keyColumnName="sequence_name", 
  -      valueColumnName="next_val]", columnNames=[sequence_name], columnValues=[song_sequence_name]
  +   | ["sequence_name"], ["song_sequence"]
   ^.^| 11
   |===
  +
  +.Content of the +IDENTIFIERS+ cache in +CACHE_PER_KIND+
  +[cols="2*", options="header"]
  +|===
  +  ^| KEY
  +  ^| NEXT VALUE
  +   | "hibernate_sequences", "["sequence_name"], ["song_sequence"]
  +^.^| 11
  +|===
   ====
   
   ===== Entities
   
  -Entites are stored in the +ENTITIES+ cache.
  +Entities are stored in the cache named after the entity name when using the +CACHE_PER_TABLE+ strategy.
  +In the +CACHE_PER_KIND+ strategy, entities are stored in a single cache named +ENTITIES+.
  +
  +The key is comprised of the following information:
  +
  +* the identifier column names
  +* the identifier column values
  +* the entity table (for the +CACHE_PER_KIND+ strategy)
  +
  +In +CACHE_PER_TABLE+, the table name is inferred from the cache name.
  +In +CACHE_PER_KIND+, the table name is necessary to identify the entity in the generic cache.
  +
  +The entry value is itself a map which contains all the entity properties -
  +or to be specific columns.
  +Each column name and value is stored as a key / value pair in the map.
   
   .Default JPA mapping for an entity
   ====
  
positive.code: 
  === Ehcache
  
  When combined with Hibernate ORM, Ehcache is commonly used as a 2nd level cache,
  so caching data which is stored in a relational database.
  When used with Hibernate OGM it is not "just a cache"
  but is the main storage engine for your data.
  
  
negative.code:       | name
        | "Leia"
  
  .2+^.^| ["GrandMother_id", "name"], ["granny", "Luke"]
        | GrandMother_id
        | "granny"
  