#16374: ExceptionReporter may re-evaluate error-causing queryset, leading to a
later DatabaseError that masks the original one
-------------------------------------+-------------------------------------
Reporter: aaron | Owner: aaugustin
Type: Bug | Status: closed
Component: Core (Other) | Version: 1.3
Severity: Normal | Resolution: fixed
Keywords: ExceptionReporter | Triage Stage: Accepted
DatabaseError current transaction | Needs documentation: 0
aborted error queryset | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: assigned => closed
* resolution: => fixed
Comment:
Since Django now uses autocommit by default, it's impossible to end up in
"current transaction is aborted, commands ignored until end of transaction
block" — unless you're building your own transaction management, in which
case it's up to you to rollback.
--
Ticket URL: <https://code.djangoproject.com/ticket/16374#comment:7>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
