Floyd Marinescu wrote:
> Thanks for all your help everyone,
>
> After reading up on optimistic and pessimistic concurrency, it seems that a
> TX_setting of serializaeable is meaningless when used with Optimistic
> Concurrency.
Wrong. If this is true with some particular app server, it's a bug. Concurrency
control and transaction isolation are orthogonal concepts. If two transactions
violate serializeable isolation using optimistic concurrency control, then at
least one of the transactions will be rolled back.
>
>
> So even if a transaction is marked serializeable, this doesn't mean that the
> database row will be both read and write locked, is this true?
It depends on the app server and database you're using. If locking isn't used,
one transaction may rollback instead of blocking.
>
>
> Floyd
>
--Victor Langelo
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
