Hi, Nothing is changed about that. Did you set graph.setUseClassForEdgeLabel(false) in your application?
Best Regards, Luca Garulli Founder & CEO OrientDB LTD <http://orientdb.com/> Want to share your opinion about OrientDB? Rate & review us at Gartner's Software Review <https://www.gartner.com/reviews/survey/home> On 30 July 2016 at 13:31, odbuser <[email protected]> wrote: > > When did the edge name convention change? Can you point me to the issue > that caused this convention change? I may be totally off base and maybe > this was actually changed in 2.2.0 vs 2.1.0 but if it was changed say 2.2.6 > vs. 2.2.4, then it seems like an invasive change for a point release. > > It used to be: > {someEdgeClass}.in_{someEdgeClass} > {someEdgeClass}.out_{someEdgeClass} > > But is now (in 2.2.6 at least) > {someEdgeClass}.in > {someEdgeClass}.out > > > create class A extends V > create class B extends V > create class EAB extends E > > --OLD WAY > --CREATE PROPERTY EAB.out_EAB LINK > --NEW WAY > CREATE PROPERTY EAB.out LINK > > --OLD WAY > --CREATE PROPERTY EAB.in_EAB LINK > --NEW WAY > CREATE PROPERTY EAB.in LINK > > --OLD WAY > --CREATE INDEX EAB.key on EAB (out_EAB,in_EAB) unique > --NEW WAY > CREATE INDEX EAB.key on EAB (out,in) unique; > > create vertex A; > create vertex A; > create vertex B; > > --The following would fail with the old naming convention > --But succeed with the new naming convention > create edge EAB from (select from A) to (select from B) > > > -- > > --- > 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.
