If you are using a PersistenceBroker you can force an insert by using:
PersitenceBroker broker = null;
/* snip */
broker.store(myObject, ObjectModificationDefaultImpl.INSERT);
Well thats what I do and it seems to work.
Regards,
Joss
> try leaving the PK empty - I thnk that OJB works out whether its a insert or
>update by the presence of this field
>
>There may be a way to force an insert but I can't remember it right now
>
>Jin
>----- Original Message -----
>From: "Durham David Contr 805 CSPTS/SCBE" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Friday, September 26, 2003 3:49 PM
>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]
--------------------
talk21 your FREE portable and private address on the net at http://www.talk21.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
