#31144: MySQL unique constraints incorrectly limited to 255 char when it should
be
1000.
-------------------------------------+-------------------------------------
Reporter: Steven Mapes | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: MySQL, MAriaDB, | Triage Stage:
Unique | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Adam (Chainz) Johnson):
* status: closed => new
* resolution: wontfix =>
Comment:
I agree with Steven here. MariaDB also ships many storage engines other
than InnoDB with different limits. It might be better to "translate"
errors coming out of the database to add a bit of django context e.g.
which model is causing the problem?
--
Ticket URL: <https://code.djangoproject.com/ticket/31144#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.0c05f26c86cf4db4b64be60b7379d8e8%40djangoproject.com.
