Hi Markus, In the case you described it want save C. if all A,B,C are changed everything will be saved.
is in schedule to review and optimize this behavior, but now is like this. bye Emanuel On 10/23/2014 12:40 PM, Markus Menner wrote: > Hi all, > > I'm using the ObjectDatabase and OrientDB 1.7.8. > > I have a general question: > > Let's assume, I have 3 POJOS: A, B, C. > > A has a Collection (let's say a Set) of B's. > B has a Collection (let's say a Set) of C's. > > A ---@OneToMany--> B ---@OneToMany--> C > > When I update an attribute in A and an attribute in C and I do a > save() on A, should the changes on C be saved as well? > > So my question is: how far is save() supposed to go? What's the exact > behavior? > > Thanks, > Markus > > > > -- > > --- > 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] > <mailto:[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.
