#17513: MySQL returns OperationalError instead of DatabaseError
-------------------------------------+-------------------------------------
Reporter: claudep | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: SVN
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage:
Keywords: mysql | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => fixed
Comment:
In [17352]:
{{{
#!CommitTicketReference repository="" revision="17352"
Fixed #17513 -- Prevented the MySQL backend from leaking MySQLdb-specific
exceptions. Thanks Claude Paroz.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/17513#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 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.
