Hi Luca, This is with 1.7-rc1. We will give 1.7-rc2 a try. Thanks, Odysseas
On Wednesday, February 19, 2014 6:21:18 AM UTC-5, Lvc@ wrote: > > Hi, > I though this issue was fixed. Are you using 1.7-rc2 ? > > Lvc@ > > > On 19 February 2014 03:02, Odysseas <[email protected] <javascript:>>wrote: > >> I am not sure if the following behavior is a result of the way we created >> the edge but if we view the edge by following the relationship from the >> vertex, all the attributes appear to be null whereas if we select the edge >> itself, all the attributes appear fine. Is this related to the behavior of >> the console or is there something inherently wrong in how we are creating >> the edges and associating them with the vertices? >> >> orientdb {person-db}> select expand(in_recordLink) from 11:3077; >> >> >> ----+-----+------------------+------+-------------+------+-----+-------------------+--------+--------+------------------- >> # |@RID |weight >> |source|userCreatedBy|vector|state|dateCreated |out |in >> |OTHER_EDGE_PROPERTY >> >> >> ----+-----+------------------+------+-------------+------+-----+-------------------+--------+--------+------------------- >> 0 |#13:0|null |null |null |null |null |null >> |null |null |null >> >> >> ----+-----+------------------+------+-------------+------+-----+-------------------+--------+--------+------------------- >> >> orientdb {person-db}> select from 13:0; >> >> >> ----+-----+------------------+------+-------------+------+-----+-------------------+--------+--------+------------------- >> # |@RID |weight >> |source|userCreatedBy|vector|state|dateCreated |out |in >> |OTHER_EDGE_PROPERTY >> >> >> ----+-----+------------------+------+-------------+------+-----+-------------------+--------+--------+------------------- >> 0 |#13:0|10.335738736518486|3 |-1 |15 |P >> |2014-02-18 20:42:18|#11:4516|#11:3077|#13:1 >> >> >> ----+-----+------------------+------+-------------+------+-----+-------------------+--------+--------+------------------- >> >> On Tuesday, February 18, 2014 8:46:47 PM UTC-5, Odysseas wrote: >>> >>> We finally found the answer to our question by reviewing the source code >>> for OrientVertex. The vertex can be loaded using the getVertex method and >>> passing the record ID. Then once we have the two vertices we can use the >>> addEge method to construct the edge. >>> >>> OrientVertex leftNode = db.getVertex(leftOrid); >>> OrientVertex rightNode = db.getVertex(rightOrid); >>> >>> >>> On Tuesday, February 18, 2014 4:50:54 PM UTC-5, Odysseas wrote: >>>> >>>> >>>> This should probably be an easy question. I need to load two vertices >>>> into memory and create an edge between them. We are shifting our >>>> application from the old graph API and trying to use blueprints and >>>> sometimes the underlying ODocument APi to eliminate all dependencies on >>>> the >>>> old graph API. >>>> >>>> We used to be able to do load each node using the record ID and then >>>> create an edge between them. The problem we are running into is that the >>>> only method we have found that allows us to load a node by the record ID >>>> is >>>> available only through the rawGraph implementation and returns an instance >>>> of ODocument. On the other hand then Blueprints API requires two vertices >>>> in order to do a vertex1.addEdge(vertex2) operation. We have looked >>>> everywhere and can't find a way to do this. Can you please help. >>>> >>>> Thanks, >>>> Odysseas >>>> >>> -- >> >> --- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- --- 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/groups/opt_out.
