Hello, I have a class A with a collection fiels x that is mapped to an indirection tables A_x. I have noticed that whenever I insert a fresh A instance with x=null, there are one INSERT statements and and DELETE statement that deletes potentially existent rows from the table A_x that reference the freshly INSERTed A instance.
This is a pity: From the logic of my application, I know that there cannot be such rows in the table A_x. If that DELETE statement should ever actually delete something, this would be an error, so I would rather see an error than have these values vanish silently. But for performance reasons, the desirable behaviour would be not to do any such statement. Is it possible to tell OJB that it shall not do that DELETE? I have investigated the code and have found that PersistenceBrokerImpl.storeToDb() calls PersistenceBrokerImpl.storeCollections() (independently from INSERT or UPDATE), which in turn does calls deleteMtoNImplementor(). I am using OJB 1.0.0 rc4. I you agree that it is desirable, I would like to add a configuration option to surpress this behaviour. Olli -- Dr. Oliver Matz ppi Media GmbH Deliusstra�e 10 D-24114 Kiel phone +49 (0) 43 1-53 53-422 fax +49 (0) 43 1-53 53-2 22 email mailto:[EMAIL PROTECTED] web www.ppi.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
