Hi, Really it is a bug. Could you create issue about it ?
On Mon, Dec 1, 2014 at 1:12 AM, Dário Marcelino <[email protected]> wrote: > Hi, > > I believe I've found a bug with DELETE EDGE in OrientDB, and consequently > in Oriento. It seems OrientDB is ignoring the class provided in queries > with format: > DELETE EDGE *class* FROM rid TO rid > And thus it may delete more edges than intended. > > I've ran the below code in both studio and console and the results were > the same: > > CREATE CLASS likes extends E > > CREATE CLASS favourite extends E > > CREATE CLASS person extends V > > create vertex Person set name = 'Luca' > > create vertex Person set name = 'Bill' > > CREATE EDGE likes from #15:1 to #15:0 > > CREATE EDGE favourite from #15:1 to #15:0 > > select expand(outE()) from #15:1 > > # 2 results > > DELETE EDGE favourite from #15:1 to #15:0 > > # expecting 1 but result was 2 > > select expand(outE()) from #15:1 > > # 0 results > > If I use 'where' it only deletes 1 edge as expected: > > DELETE EDGE from #15:1 to #15:0 where @class='favourite' > > Thanks > > > > > -- > > --- > 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. > -- Best regards, Andrey Lomakin. -- --- 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.
