anchor.diff: -== Simple Query 
  +== Simple Json Query
  +
  +****
  +MongoDb uses a json based flexible query structure that allows a good learning 
  +curve because of a simple form for every day jobs. Inspired by this, the idea for this
  +approach came up.
  +****
  +
  +IMPORTANT: It is always possible to use application or base names for entity, relations, attributes. 
  +           Order is 1.) application 2.) base. If base name is not uniquely assigned in the schema one of the vector is picked. 
  +           This is important for writing generic code even without having to analyze the complete schema.
  +           Be aware that application name can always be used to access any element or attribute.
   
   === The json query structure
   
  
positive.code: | $point     | used for query on bulk data. returning indices of local column values
  | $options   | string containing letters: `e` enum values as string 
  |===========================================
  
negative.code: -----------
  
  TIP: `test.id` is a duplicate because the id is also stored in test column
  
  .use inverse to do the same job
  ===============================
  
  [source,json]
  -----------
  {
  	"AoSubTest": "4611",
  	"$attributes": {
  		"children.name": 1,
  		"children.id": 1
  	}
  }
  -----------
  
  [source,json]
  -----------
  {
  	"AoSubTest": "4611",
  	"$attributes": {    
  		"children": {
              "name": 1,
              "id": 1
          }
  	}
  }
  -----------
  
  ===============================
  
  ==============================
  
  