Thank you very much, in case you want to track the resolution of this problem, you can watch this: https://github.com/orientechnologies/orientdb/issues/new
Thanks Luigi 2017-11-14 20:30 GMT+01:00 Eric24 <[email protected]>: > Steps to produce bug: > > 1. Enable Lightweight Edges > 2. CREATE CLASS SimpleV EXTENDS V > 3. CREATE CLASS SimpleE EXTENDS E > 4. INSERT INTO SimpleV CONTENT {"name":"A"} // this is #25:0 > 5. INSERT INTO SimpleV CONTENT {"name":"B"} // this is #25:1 > 6. CREATE EDGE SimpleE FROM #25:0 TO #25:1 > 7. SELECT FROM SimpleE // empty result, provides that Lightweight > Edge was used > 8. DELETE VERTEX #25:1 > 9. SELECT FROM SimpleV // returns #25:0, with OUT still showing link > to #25:1 > > > > On Tuesday, November 14, 2017 at 2:18:36 AM UTC-6, Luigi Dell'Aquila wrote: >> >> Hi Eric, >> >> The main problem with lightweight edges is that they do not have an >> identity, so they don't "physically" exist. >> The big disadvantages are that: >> - you cannot point to a single lightweight edge by RID >> - you cannot count them, eg. SELECT FROM E will return a wrong result >> >> The DELETE VERTEX is supposed to work fine though, if you have a test >> case that proves the problem please submit it, I'll check it asap >> >> Thanks >> >> Luigi >> >> >> 2017-11-13 19:21 GMT+01:00 Eric24 <[email protected]>: >> >>> It has been mentioned many times that using lightweight edges is "more >>> difficult" with SQL. Can anyone provide specific examples of when this is >>> true (i.e. what are the SQL issues created by using them)? >>> >>> I ask because just about everything I've tried with lightweight edges >>> works the same way with regular edges (even SELECTs that return linked >>> records using both kinds of edges in a single query). >>> >>> The one thing I've found that doesn't work with lightweight edges (which >>> is a bit of a surprise to me) is that the links are not "cleaned up" when >>> doing a DELETE VERTEX operation (i.e. "broken" links are left in the >>> remaining vertex records). Is this an expected behavior? If so, it should >>> probably be listed in the documentation as one of the cons to lightweight >>> edges. If not, what is the appropriate way to delete a vertex record while >>> ensuring that links to the deleted record are removed from the remaining >>> records? >>> >>> -- >>> >>> --- >>> 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 [email protected]. >>> 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
