Thomas Dudziak wrote:
Hi,
could please somebody explain why the auto- settings (auto-retrieve, auto-delete, auto-update) should only be used with the default settings when using ODMG (or JDO) ?
Usinf auto-update="true" results in double inserts for dependend objects. As the ODMG or JDO transaction manager registers the dependend objects for insertion and the auto-update flag triggers the PersistenceBroker to insert the dependend objects a second time...
To give an example, how would I implement a composition (object of type A "owns" n objects of type B -> collection) which naturally (at least I think) use auto-delete and perhaps auto-update, for the ODMG implementation ?
I think using auto-delete="true" should be OK in this case. If you see exceptions for DELETE statements that try to delete objects twice, you'll see the same behaviour as with the INSERTS.
cheers, Thomas
Thanks, Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
