#29575: MySQL error code 1062 (duplicate entry for key) raises
MySQLdb.IntegrityError, not django.db.IntegrityError
--------------------------------+--------------------------------------
Reporter: Simon Willison | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 2.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Comment (by Simon Willison):
Note that this affects Django 1.11x (and previous versions), not just
Django 2.x - but since fixing this would be a backwards incompatible
change for everyone who is currently catching `MySQLdb.IntegrityError`
presumably it wouldn't make sense to fix this in 1.11x
--
Ticket URL: <https://code.djangoproject.com/ticket/29575#comment:1>
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.40dd50ac3f885997381be23818aac02b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
