UPDATE EDGE statement [moved]

This is Issue 1114 moved from a Google Code project. Added by 2012-10-14T22:09:41.000Z by infected…@gmail.com. Please review that bug for more context and additional comments, but update this bug.

Original labels: Type-Enhancement, Priority-Low, v2.1.0

Original description

Having an UPDATE EDGE statement would be nice because there is less overhead then deleting and recreating the edge.

Discussion here: https://groups.google.com/forum/#!topic/orient-database/Z5ZElaxVSZ0

[matanshukry]

As far as I can tell, update works (including in/out):

UPDATE FRIEND SET in=#11:5 WHERE in.name="Samantha" and out.name="Mat"

Although, using a query inside the set clause for in/out will cause it to return array, which is not the desired behavior. Example:

UPDATE Friend SET in=(SELECT FROM User WHERE name="Jason") WHERE in.name="Samantha" and out.name="Mat"

When later querying the table Friend, we can see column “in” will contain [#11:4], emphasis on the brackets [], which means an array.

Upsert also works, although when creating a new vertex it doesn’t set the in/out properties. You could set the in/out properties your self, like this:

UPDATE Friend SET comment="Wazzzaup", in=#11:5, out=#11:6 UPSERT WHERE in.name="Jason" AND out.name="Mat"

It will result in a longer query when using sub-query for in= and out=, but at least it works (sub-query has same problem as above).

To summarize, the only problem I can see is using a sub-query for in/out. So:

1. Is there any other feature required here? If not, can we agree the UPDATE command is suffice and there is no need for an UPDATE EDGE command?
2. Is there anyway to set the in/out properties, perhaps one that I missed?

[luigidellaquila]

Yes, you are right, thank you for the pointer!

Luigi