Hi, what version are you using? In the latest SNAPSHOT the ObjectDatabase clears all fields after a reload.
2014-05-23 9:52 GMT+02:00 Julian Neuhaus <[email protected]>: > Hello everybody, > > I expected a little problem for my self using *OObjectDatabaseTx *and > *reload(o)*. It seems like that only the first-level of the given Object > will be reloaded. There is no api-way to reload the values of the proxied > objects inside the given object, which makes some problems very difficult > to solve. Reload the hole objecttree is expensive and shouln't be the > default, but it seems like it isn't possible at all. > > Test-Case: > > class A > { > String nameA; > B b; > > } > > class B > { > String nameA; > } > > 1. A a =new A() > 2. a.setName('nameA') > 3. b = new B() > 4. b.setName('nameB') > 5. a.setB(b); > 6. insert(a); > 7. a.setName('wrong_nameA') > 8. b.setName('wrong_nameB'); > 9. reload(a); > > After this a.getName() returns ('nameA') which is correct. But b.getName() > returns 'wrong_nameB'. So reload() doesn't effects the deeper levels of the > objecttree. Is this the expected behaviour or are there any other methods > to reload the hole objectree. I also tried reload with FetchPlan '*:-1' but > recieved the same result. Only when I reload B with an extra call of > reload, I get the correct stored value from the db. > > > Used version: OrientDB 1.7rc2 > > Thanks for help or ideas > Julian > > -- > > --- > 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. > -- Luca Molino -- --- 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.
