Thank you Scott for the reply.
Please find the Query results. Here I am creating User verted, Project
Vertex and creating edge ownedByUser.
1. select * from #278:56 (Query on Edge)
{"@type":"d","@rid":"#278:56","@version":1,"@class":"ownedByUser","out":"#96:54","in":"#45:34","@fieldTypes":"out=x,in=x"}
2. select out_ownedByUser from #96:54 (Query on Project)
{"@type":"d","@rid":"#-2:0","@version":0,"out_ownedByUser":["#278:56"],"@fieldTypes":"out_ownedByUser=g"}
3. select in_ownedByUser from #45:34 (Query of User)
{"@type":"d","@rid":"#-2:0","@version":0,"in_ownedByUser":[{"@type":"d","@version":0,"@class":"ownedByUser","out":"#96:54","in":"#45:34","@fieldTypes":"out=x,in=x"}]}
This looks like a major bug in OrientDb for me. Edge is created, out
property of originating vertex is finely updated. But not the destination
vertex.
Its in_edge property is stored as document rather @rid. I believe its
because @rid is not available in its metadata.
Please help.
On Thursday, April 20, 2017 at 3:07:56 PM UTC+5:30, scott molinari wrote:
>
> The V1, V2 and e1 are 3 distinct classes. So, you have 3 distinct
> documents. I am guessing, the creation of an edge takes two saves to the
> document, thus you have 2 versions. In other words, when you look at V2, it
> is one document. When you look at the edge, it is a different document.
> (using normal and not light weight edges).
>
> Scott
>
>
--
---
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.
