I am using edges that connect document collections to another edge (this
second edge connects to document collections).
Here a small schema:
collection_1 <--------- edge_1------------ collection_2
^
|
|
edge_2
|
collection_3
Because I have an anonymous graph, for removing edges that point to an
already removed documents, what I do is search for edges that link to
_unknown (automatically set up by arangodb when I remove the document
collection that was linked with that edge). However when I remove an edge
that is connected with another edge (for example edge_1 in the schema),
arangodb does not set up edge_2 to_ to _unknown but to the _id that edge_1
had (which is actually removed). Therefore I cannot quicly check and remove
those edges that link to _unknown.
To make it clear, read the following example:
I have the schema represented above and I remove collection_2 document
Then edge_1 is automatically set as *from*: _unknown, *to*; collection_1
Because edge_1 points *from* _unknown this is removed by my code
Then, I was hoping that because edge_1 was removed then edge_2 would be set
as *from*: collection_3 *to:* _unknown (and again being removed by my code)
However edge_2 remains as *from*: collection_3 *to*: edge_1 (which does not
exists) and therefore edge_2 is not removed by the code.
I think that arangodb should set to _unknown also those edges that were
connected to another edge.
(I am using arangodb 2.8)
Thanks!
--
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.
