We saw that most of the times, the best way is: - creating a new document/vertex per version, with inside all the changed fields - keep the same document/vertex as the last version, so all the pointers are still valid because the RID doesn't change - don't connect all the versions to the main document/vertex, but rather use a linked list approach where you connect all the versions with "previous" link/edge. Example: (#13:13 Company v.20)--prev-->(#14:22 Company v.19)--prev-->(#14:31 Company v.18)
Best Regards, Luca Garulli Founder & CEO OrientDB <http://orientdb.com/> On 4 August 2015 at 14:27, <[email protected]> wrote: > Hi, > I think that if you have a lot of information to be stored in your node > might be much better then having "delta" nodes connected to the main node, > otherwise if you have to keep in memory one field you could use a > embeddedlist and add the old values time to time. > Regards, > Alessandro > > -- > > --- > 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. > -- --- 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.
