#29575: MySQL error code 1062 (duplicate entry for key) raises
MySQLdb.IntegrityError, not django.db.IntegrityError
-------------------------------------+-------------------------------------
Reporter: Simon Willison | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* type: Uncategorized => Bug
* component: Uncategorized => Database layer (models, ORM)
* resolution: => worksforme
Comment:
I also can't reproduce. The code to convert
`_mysql_exceptions.IntegrityError` to `django.db.IntegrityError` is in
[https://github.com/django/django/blob/55b6f7af0c6ab7f25818445cfbb9e18ddafedcc9/django/db/utils.py#L82-L89
django/db/utils.py].
--
Ticket URL: <https://code.djangoproject.com/ticket/29575#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.b1b0f0ba3c5a524fce2f4343265e0285%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
