Hi Dmitri, Document layer does not manage link consistency, just for a matter of performance, but Graph layer does (eg. it removes dangling edges when you delete a vertex). My advice is to use edges instead of links, it will also give you another advantage, that is having bi-directional traversal of pointers
Thanks Luigi 2015-10-30 2:47 GMT+01:00 <xzf...@gmail.com>: > Hello, > > This question was asked in 2013, and Luca's reply was as follows: > > On Monday, May 20, 2013 at 6:20:24 PM UTC-4, Lvc@ wrote:If you remove a >> document is your responsibility to clean all the references. >> > > Does this answer still hold? If yes, how can I find all the references to > a class that is about to be deleted? (or what is the recommended way of > otherwise dealing with this issue?) > > I am using 2.1.2 (trying it out) and I was quite amazed to find that the > database allowed me to drop the referenced class and kept the RID of the > referenced object (dangling pointer, basically). > > The scary thing was that once I created (and populated) another class, the > cluster id was reused, and the RID happily pointed to a new, entirely > unrelated object. > > Thanks! > Dmitri > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to orient-database+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
