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

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

Hi Thomas,

<snip>

>
> Mmh. This is a good idea. But I think it is conflicting with the
> hashtable concept. The hashtable is used to allow quick lookup of locked
> objects during a tx.

I think I have found a solution for this that is able to tell the order of
the added objects while maintaining the speed of the hashtable for lookups.
Only removing objects from the table would be more expensive.

>  > 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 is exactly the depency graph I'm talking about!
> By analysing the ReferenceDecsriptors and the CollectionDescriptors it
> is possible to determine which object has to be inserted first etc.

So this is easy. TransactionImpl.register already resolves References and
Collections, just the order has to be changed.

I just added the RI test case to CVS and I hope I can commit the fix today.

<snip>

best regards,
Florian