#28091: Hiding 'cursor does not exist' error doesn't work
-------------------------------------+-------------------------------------
Reporter: Claude | Owner: nobody
Paroz |
Type: Bug | Status: new
Component: Database | Version: 1.11
layer (models, ORM) |
Severity: Release | Keywords:
blocker |
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
In commit [6b6be692fcd102436c7abef1d7b3fa1d37ad4bdf], Django tries to mask
the 'cursor does not exist' exception because it masks the real database
exception. Unfortunately, the commit is not fulfilling its promise, as the
`raise` command just after the `pass`, will in fact raise the second
exception (the one we are trying to mask) not the original one.
--
Ticket URL: <https://code.djangoproject.com/ticket/28091>
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.82d047cebdc55cea17b2ef02109582ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
