anchor.diff:                        .addEntity( "Poem", Poem.class )
                         .list();
   ----
  -====
  -
  -[NOTE]
  -====
  -As +OgmSession+ extends +org.hibernate.Session+ (which originally has been designed with relational databases in mind only)
  -you could also invoke +createSQLQuery()+ to create a native query. But for the sake of comprehensibility, you should prefer
  -+createNativeQuery()+, and in fact +createSQLQuery()+ has been deprecated on +OgmSession+.
   ====
   
   Native queries can also be created using the +@NamedNativeQuery+ annotation:
  
positive.code: ==== Annotation based configuration
  
  Hibernate OGM allows to configure store-specific options via Java annotations.
  When working with the MongoDB backend, you can specify the following settings:
  
  * the write concern for entities and associations using the +@WriteConcern+ annotation
  
negative.code: * using a native MongoQL query
  * using a Hibernate Search query (brings advanced full-text and geospatial queries)
  
  While you can use JP-QL for simple queries, you might hit a limitation of our conversion.
  The current recommended approach is to use native MongoQL
  if your query involves nested (list of) elements.
  
  [NOTE]
  ====
  In order to reflect changes performed in the current session,
  