#31144: MySQL unique constraints incorrectly limited to 255 char when it should
be
1000.
-------------------------------------+-------------------------------------
Reporter: Steven Mapes | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
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 felixxm):
* cc: Claude Paroz (added)
* status: new => closed
* version: 3.0 => master
* resolution: => wontfix
Comment:
Thanks for this ticket, however Django supports MySQL 5.6+. Moreover this
restriction depends on character set, database version, database engine,
and parameters (see related ticket #28661), so it's quite complicated to
determine the real upper bound. Even with MySQL 8.0 we still have the
following restriction:
> InnoDB tables that use DYNAMIC or COMPRESSED row format and 767 bytes
for InnoDB tables that use the REDUNDANT or COMPACT row format.
which means 255 characters with `utf8` and 191 characters with `utf8mb4`.
--
Ticket URL: <https://code.djangoproject.com/ticket/31144#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 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.f0dada0ece52ffd99557fa7a364252e7%40djangoproject.com.
