#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: Core (Other)
Version: 1.3 | Severity: Normal
Resolution: | 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
-------------------------------------+-------------------------------------
Comment (by lukeplant):
For the DB-level switch, it should throw some exception. The hard part is
find the right point to do it.
So I think for now, your 'safe_repr' idea is the best one. Perhaps even
`__safe_repr__`, to avoid accidental conflicts, and to make it obviously
similar to `__repr__`. The exception handling will call this method,
perhaps via a new `saferepr` function that encapsulates the checking for
`__safe_repr__` attribute. We can avoid isinstance checks entirely this
way.
--
Ticket URL: <https://code.djangoproject.com/ticket/16374#comment:5>
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 [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.
