#13265: TransactionManagementError doesn't allow for easy debugging of views
---------------------------------------------------+------------------------
Reporter: orokusaki | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
I don't know if I'm seeing the same problem (it's difficult to know for
certain without test code to demonstrate your problem), but based on your
explanation, I see a TransactionManagementError that reports that
"Transaction managed block ended with pending COMMIT/ROLLBACK". I'm not
entirely sure what extra information we can provide in this circumstance
-- the error is telling you exactly what has gone wrong. It's not like
we're rethrowing an error and thereby hiding a stack trace. The problem is
that there is a code path in your view which has either not thrown errors,
or caught all errors that have been thrown, but that allows a clean
return from the view with pending transaction activity. The request URL,
GET/POST and cookie values are all shown on the debug page, which should
be enough to reproduce the bad request and determine how the code path is
returning with this pending state.
Given that this report doesn't give a specific course of action, and the
desired course of action isn't obvious (to me, anyway), I'm closing
wontfix.
--
Ticket URL: <http://code.djangoproject.com/ticket/13265#comment:1>
Django <http://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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
