Hi Roger,
Janssen, Roger wrote:
Hi,
in the release notes it says :
"Batch handling doesn't work proper with optimistic locking. This will be fixed before long after 1.0"
What exactly does this mean? Does it mean that when i have a persistence broker transaction, and within that transaction i do save several objects, and one of these fails during the commit because of a concurrent update (optimistic locking using timestamps), that there will be no full rollback?
I assume that is true. Current batch handling does not take care of optimistic locking, the PreparedStatement proxy always returns 1 on executeUpdate call.
regards, Armin
Roger Janssen iBanx
--------------------------------------------------------------------- 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]
