#27979: Using F() with mysql can leak an unwrapped OperationalError
-------------------------------------+-------------------------------------
Reporter: Chris Dary | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: db, mysql, | Triage Stage:
exceptions, OperationalError | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* type: Uncategorized => Bug
* component: Uncategorized => Database layer (models, ORM)
Comment:
What do you mean by "a wrapped exception"? Are you thinking it would be
reraised as `IntegrityError` similar to
90279aeaf07222dd7388956bfd465d30365087a5?
--
Ticket URL: <https://code.djangoproject.com/ticket/27979#comment:2>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.1d8ffe7cb5fbba16037b59c2a0d51aff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
