Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When setting the isolation level over multiple transactions, what can be the cause for aborting a transaction?
i assume that the isolation level defines which anomalies are allowed/not allowed to happen by appropriate locking, and not by aborting the transaction – is this a correct assumption?
So far the only reason I can think of is when the execution deadlocks and one of the transactions must be aborted.
If one transaction T1 is requesting some resource R1 that is locked by another transaction T2, then T1 could time out and abort.
This is not yet a deadlock situation. Deadlock is when both T1 and T2 get stalled, each waiting for the other to release a lock the other has on some resource.