Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @schneems (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review.

Please see the contribution instructions for more information.

Should this be TransactionTimeout? We've got Deadlocked, but that seems to be an exception.

What you recommend it to be? LockWaitTimeout?

@rafaelfranca either one seems fine to me. TransactionTimedout sounds less consistent... I think the noun form fits with wider exception naming: it's FrobError, not FrobFailed. It's a fairly fine distinction, but I think an exception describes what occurred that prevented the action, rather than why the action couldn't be performed.

Yeah, it makes sense. I think TransactionTimeout is better than LockWaitTimeout since it is more generic. @gcourtemanche can you rename the exception from TransactionTimedout to TransactionTimeout?

@rafaelfranca Yes, renamed to TransactionTimeout