RE: [OJB-developers] RE: Referantial Integrity under ODMG

[Florian B. <bf...@fl...>]

> The ojb.odmg.TransactionImpl holds a ObjectEnvelopeTable that maintains a
> Hashtable of all Objects locked to a Transaction.
>
> (The PersistenceBroker is not involved in these issues. I guess this was
> a typo?)

Well, not really a typo, just got things wrong ;-)

> I will provide a fix for the second problem in the next release.
> So you can concentrate on RI ;-)

Great, so I'll look further into the RI issue. What I think I could do is
the following:

1.) Maintain the order of write locks. This would make it possible for the
user to control this order and therefore resolve RI violations by inserting
objects in a proper order. Especially when OJB doesn't know about a RI this
would be good

2.) Change the order how dependent objects are inserted/updated/deleted.
Referenced objects are always the master, collections are always the detail
to an object. Currently I cannot think of a case where this could be
different.

This would save us from calculating a sophisticated dependency graph I
think.

best regards,
Florian