#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
-------------------------------------+-------------------------------------
Comment (by Chris Dary):
Yep - as mentioned in the docs here:
https://docs.djangoproject.com/en/1.10/ref/exceptions/#database-exceptions
It's nice to have Django wrap DB specific exceptions so that you have an
agnostic interface to them and don't have to catch engine specific
exceptions. Based on the phrasing there ("guaranteed common
implementation"), I presume it's a bug when one of these engine specific
exceptions leaks.
--
Ticket URL: <https://code.djangoproject.com/ticket/27979#comment:3>
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.55fa6e8973e8f4143020787825013d17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
