the same problem... how can i fix that?
Il giorno mercoledì 11 marzo 2015 16:50:30 UTC+1, Nicola Petracchi ha
scritto:
>
> Hello, I'm testing OrientDB 2.0.4 for inclusion in a project, as stated in
> the subject I renamed a Edge class (ex: from X to Y) and this has caused on
> the connected Vertexes a strange behavior: the old edges of class X created
> until the name change are still present in the ridbag with name in/out_X ,
> and, the new edges (using the new name Y) are recorded under ridbag with
> new name in/out_Y
>
> This affect the query because* select in('X') from entity* returns the
> edges that once were X, instead none, and *select in('Y') from entity*
> returns only the new edges and not the whole set (old renamed + newly
> created).
>
> On Edge side all the edges in query view have the classname correctly
> changed and this is correct.
>
> I'm very new to OrientDB so this behavior could be normal as intended, or
> I'm changing a class name in a wrong way.
>
> Any response is appreciated.
> Regards N
>
--
---
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.