<[EMAIL PROTECTED]> wrote:
>>Do you agree that when two or more concurrent transactions update two or
>>more
>>resources without following a strict order, there's potential for
deadlock?
>Yes, the potential being that pessimistic concurrency control is used.
>With optimistic locking this is impossible since concurrent transactions
>get "their own version", and hence never compete for the exact same
>resource.
I think I was giving you more credit than you deserve. I don't know
whether it's your English or real lack of DBMS understanding here but
it seems to me you have the wrong end of the stick. You don't even
seem to know what a database resource deadlock is and how it comes about.
Once again:
TX1 updates DB resource A, and waits on DB resource B
TX2 updates DB resource B, and waits on DB resource A
Deadlock.
Now is that really that difficult for you to grasp?
Regards,
Hamid
===========================================================================
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".
