#17004: transaction.commit_manually decorator masks exceptions
----------------------------------------------+--------------------
Reporter: msoulier@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: 1.3
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
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?
Thank you.
--
Ticket URL: <https://code.djangoproject.com/ticket/17004>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
