Hello, > -----Original Message----- > From: Andy Malakov [mailto:[EMAIL PROTECTED]
> Problem: Right after insert, PersistenceBrokerImpl calls > storeCollections () method that performs redundant DELETE FROM... > operation. The problem has been mentioned by myself in the developer list together wit a fix and a discussion whether to fix it. performance: surpress m:n collection deletion on insert > Solution: It should be possible to pass current operation > type update/insert to storeCollections () and avoid calling > deleteMtoNImplementor() in case of insert. This operation > type is always available in any caller method. > > P.S. Can somebody from OJB development confirm this message, please? done. I am uncertain whether we should fix it because it does mean a (very minor) change of behaviour. I tend to 'yes'. Olli --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
