ArangoDB: use _key instead of _id #293
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
TODO: rebase onto #292 once merged
In ArangoDB, the field
_keyshould be considered as primary key for the documents. In fact,_idfield is read-only (the database ignores the values set by the client) and auto-generated by the database (concatenating<collection-name>/<_key>.See https://docs.arangodb.com/stable/concepts/data-structure/documents/#document-keys
For the moment, I have annotated the id fields in the test entities specifying
_keyvalue, e.g.:Ideally in future we could allow databases implementation specify the default field name, i.e. allowing:
to be mapped automatically to field
_keywhen using ArangoDB.