#16374: ExceptionReporter may re-evaluate error-causing queryset, leading to a
later DatabaseError that masks the original one
-------------------------------------+-------------------------------------
Reporter: aaron | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Generic views
Version: 1.3 | Severity: Normal
Resolution: | Keywords: ExceptionReporter
Triage Stage: | DatabaseError current transaction
Unreviewed | aborted error queryset
Needs documentation: 0 | Has patch: 0
Patch needs improvement: 0 | Needs tests: 0
UI/UX: 0 | Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by aaron):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Another idea -- perhaps it would make sense to add a global toggle that
determines whether QuerySet.__repr__ evaluates them, and leave it on at
all times except when rendering the error page.
--
Ticket URL: <https://code.djangoproject.com/ticket/16374#comment:1>
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.
