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

[Thomas M. <tho...@ho...>]

Hi Florian,

<snip intro>

 >
 > 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



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.


 > 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.


cu,

Thomas

 > This would save us from calculating a sophisticated dependency graph I
 > think.
 >
 > best regards,
 > Florian
 >
 >
 >
 >
 >