anchor.diff:  ====
   Hibernate OGM always store identifiers using the +_id+ field of a MongoDB document ignoring
   the name of the property in the entity.
  +
  +That's a good thing as MongoDB has special treatment and expectation of the property +_id+.
   ====
   
   An identifier type may be one of the <<mongodb-built-in-types,built-in types>>
  
positive.code:                       .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:
  
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,
  