anchor.diff:  | indexes.auto=assert
   | config.setAutoIndex("assert");
   
  +| *update*
  +| Builds indexes based on whatever is represented in OGM by `@Index`. Indexes will be changed to constraints and vise versa if the definition in db differs from metadata.
  + Handy during development
  +| indexes.auto=update
  +| config.setAutoIndex("update");
  +
   | *dump*
   | Dumps the generated constraints and indexes to a file. Good for setting up environments. none: Default. Simply marks the field as using an index.
   | indexes.auto=dump
  
positive.code: 
  If you would like the OGM to manage your schema creation there are several ways to go about it.
  
  Only classes marked with `@Index` will be used. Indexes will always be generated with the containing class's label and the annotated property's name.
  Index generation behaviour can be defined in `ogm.properties` by defining a property called: `indexes.auto` and providing a value of:
  
  Below is a table of all options available for configuring Auto-Indexing.
  
negative.code: The primary key is solely provided by the `@Id` annotation.
  See <<reference:annotating-entities:entity-identifier, Entity identifier>> for more information.
  
  [[reference:indexing:composite]]
  == Composite Indexes and Node Key Constraints
  Composite indexes based on label and multiple properties are supported with `@CompositeIndex` annotation.
  The annotation is to be placed at the class level.
  All properties specified must exist within the class or one of its superclasses.
  It is possible to create multiple composite indexes by repeating the annotation.
  
  Providing `unique=true` parameter will create a node key constraint instead of a composite index.
  
  [NOTE]
  This feature is only supported by Neo4j Enterprise 3.2 and higher.
  
  [[reference:indexing:existence-constraint]]
  == Existence constraints
  Existence constraints for a property is supported with `@Required` annotation.
  It is possible to annotate properties in both node entities and relationship entities.
  For node entities the label of declaring class is used to create the constraint.
  For relationship entities the relationship type is used - such type must be defined on leaf class.
  
  [NOTE]
  This feature is only supported by Neo4j Enterprise 3.1 and higher.
  
  [[reference:indexing:creation]]
  == Index Creation
  
  