Hi,

I very much like the interface store of the broker which shields me
from the differences between insert or update. Sometimes however I
would like to prevent an update when an insert is not possible. E.g a
legacy application does not allow some records to be updated but only
to be inserted.

When programming with the standard jdbc layer I get an exception
telling me insert is not possible e.g. due to primary key conflict.
Ojb when automatically seems to perform an update which under certain
circumstances is not what I need.

Is there a way to prevent this behavior, or do I need to perform a
lookup before a store to implement this ?

Thanks for your help,

Stefan Schl�sser

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to