Out of curiosity, is this 100% the result of version 2.2.0? I just want to make sure before undertaking upgrading all of my test and production systems.
On Thursday, September 28, 2017 at 12:11:04 PM UTC-4, Luigi Dell'Aquila wrote: > > Hi, > > This issue was fixed long time ago, I suggest you to upgrade to 2.2.28, > latest stable > > Thanks > > Luigi > > > 2017-09-28 18:01 GMT+02:00 <dboden...@problemsolutions.net <javascript:>>: > >> I have version 2.2.0 of orientdb on my system. I ran into a situation >> where I need to change the out property of an edge from one vertex to >> another. From what I read version 2.2.0 is the first version which supports >> updating the in/out property of an edge. >> >> I ran the command "UPDATE EDGE searched SET out=#17:47 WHERE @rid=#23:60" >> >> However when I query for the out edges from the vertex it was on >> previously and the one it is currently on, they both say they have that >> edge as an out. When I query for that edge however it just says that the >> out is one thing. How is this possible? Is there something I did with the >> update that is causing this dual link? >> >> -- >> >> --- >> 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-databa...@googlegroups.com <javascript:>. >> 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.
