Hi Fabrizio, this seems related to last optimization about removing class from serialized record.
@Andrey do you know why? Lvc@ On 20 February 2014 11:40, Fabrizio Fortino <[email protected]>wrote: > Moreover, I noticed that a field named LONG_NAME has been stored has > VertexA@LONG_NAME > > > On Thursday, February 20, 2014 10:34:07 AM UTC, Fabrizio Fortino wrote: >> >> Hi guys, >> >> I have stumbled in a pretty critical project using the latest version >> from develop branch. >> >> I have a process that creates vertex (VertexA) with related edges >> pointing to other vertexes(VertexB). To create and edge I use the following >> code: >> >> graph.addEdge(null, vA, vB, "has"); >> >> As you can see I use the label "has". When I browse VertexA I noticed >> that for some records the edge property is name is VertexA@out_hasinstead of >> out_has . >> >> The same code was working with 1.7RC1, so I think something happened in >> the latest commits. >> >> Any idea? >> >> Thanks, >> Fabrizio >> >> >> >> -- > > --- > 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. > -- --- 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.
