Thanks Simran, I think I'm understanding you.
So AQL itself doesn't enforce integrity—this makes sense since it's just a
hard call to the db. But some of the API calls (on named graphs) do check
for dangling vertices/edges, etc.
So, which of the ArangoJS graph/edge collection calls maintain integrity
then?
On Monday, June 13, 2016 at 9:45:41 AM UTC-4, Simran Brucherseifer wrote:
>
> Neither named graphs (graph edge collections), nor anonymous graphs
> ("loose" edge collections) maintain integrity, if you use AQL queries for
> manipulation.
>
> To ensure integrity, you have to define a graph ("named graph") and use
> the general graph API / module when deleting vertices. The edge collections
> as per the graph definition will then be checked when you delete vertices,
> and edges linked to these vertices be removed as well, so that the edges
> don't become "dangling".
>
> Also note that the same edge collection can be used for multiple graph
> definitions, and still be accessed directly with AQL or the normal HTTP
> interface and therefore affect integrity.
>
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
