Hi Dave, Actually in should to either INSERT or UPDATE if the PK is set properly, But if you inserted a row using OJB and deleted the record using JDBC And trying to store using OJB again than it wil use UPDATE, not INSERT. You should clear the cache before as it doesn't know about external operations, or don't use broker cache at all,
-Sergey -----Original Message----- From: Durham David Contr 805 CSPTS/SCBE [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2003 10:49 AM To: [EMAIL PROTECTED] Subject: storing a new object fails I'm writing a routine that clears out a db and reloads a defined test data set. I'm trying to insert new objects but sometimes, not always, OJB will execute an update statement instead of an insert. I'm explicitly setting the id pk's and bypassing the sequencemanager, so I figure that has something to do with it, but I can't explain the discrepancy. Can anyone point me to the likely cause of this? Thanks, Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
