Re: [Springframework-developer] DeadlockLoserDataAccessException vs CannotAcquireLockException

[Rod J. <ro...@in...>]

Thomas

> ConcurrencyFailureException
> '- TransactionLockingFailureException [X]
>     '- CannotAquireLockException [X]
>     '- CannotSerializeTransactionException [X]
>     '- DeadlockLoserDataAccessException [X]
> '- OptimisticLockingFailureException [X?]
> 
> The [X] indicates that I think we should provide the option for separate 
> categories in sql-error-codes.xml for this exception.  Some of the lower 
> exception classes might not make sense for all databases, but 
> TransactionLockingFailure and OptimisticLockingFailure will provide 
> enough information to retry the transaction if the app developer want to 
> do that.

I like this proposal. Though should it ben 
PessimisticLockingFailureException to match 
OptimisticLockingFailureException? Yes, the latter is intended to be 
thrown by ORM tools, not JDBC-level operations. So we could convert from 
whatever the ORM tool throws. Or developers could throw it themselves, 
still allowing for consistent handling within Spring's DAO abstraction.

R
> 
> Oracle might have these categories defined:
>     '- CannotAquireLockException [X]
>     '- CannotSerializeTransactionException [X]
>     '- DeadlockLoserDataAccessException [X]
> 
> while MySQL might have this
> '- TransactionLockingFailureException [X]