Thank Max, For creation, "educated guesses" was just implemented for a few days. The current algorithm is that any object's table T, has foreign key and the foreign key is referring to a key-generated object R, then R will be created before T, providing T is not equal to R. I will see if this algorithm is significant or not. If it are not, I would consider your suggestion. Yes, I guess we would do the same things to deletion in the new code. Thomas -----Original Message----- >From: Max Foxell [mailto:[EMAIL PROTECTED]] >Sent: Friday, August 03, 2001 10:59 AM >To: [EMAIL PROTECTED] >Subject: [castor-dev] Feature request: enhance rules governing dependent object creation/deletion > >Hi, > >I've been using Castor for a few months now and have found it extremely >useful ;-). I noticed recently that there are plans to refactor the JDO >portion of Castor and I thought this would be a good time to ask for a >feature request. One of the problems I've found with Castor is that >there isn't enough control over the order of creation and deletion of >dependent objects. Without this control referential integrity can be >broken. As a work around we have to have two sets of configuration files >(one used for adding stuff to the database and one for removing stuff). >One solution would be to specify the creation/deletion order in the >mapping file. If the code were especially smart Castor could make >educated guesses at the appropriate order automatically by examining the >references in the mapping file and looking at the database meta data. >Hope you manage to fit this into your plans :) > >Thanks, > Max Foxell > >----------------------------------------------------------- >If you wish to unsubscribe from this mailing, send mail to >[EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
