transaction.commit_manually decorator masks exceptions
|Reported by:||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||1.3|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
If I put a commit_manually decorator on a piece of code, and that code raises an exception that isn't caught, all the developer will see is a failure to commit or rollback the transaction, instead of the actual exception that caused the problem.
This can hinder troubleshooting at a customer site.
Is it feasable for the decorator to check for an exception before inadvertently swallowing it, and reporting it?