Opened 8 years ago

Last modified 13 months ago

#28661 new New feature

Auto-truncate indexes on MySQL when max index size is reached

Reported by: Claude Paroz Owned by: nobody
Component: Database layer (models, ORM) Version: dev
Severity: Normal Keywords:
Cc: Clifford Gama Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no

Description

We have been hit several times in Django by this MySQL limitation when wanting to extend the length of some indexed char fields. One example is #19515.

I suggest to automatically limit indexes when the size of the indexed field is too long to be completely indexed by MySQL. This auto-truncation would be limited to single-indexed fields, because I don't see trivial automatic rules when more than one field is indexed (proportional shortening, maybe?).

Change History (7)

comment:1 by Claude Paroz, 8 years ago

Has patch: set

​PR

comment:2 by Claude Paroz, 8 years ago

Also note that this is a step toward activating the utf8mb4 charset by default (#18392).

comment:3 by Tim Graham, 8 years ago

Triage Stage: Unreviewed → Accepted

comment:4 by Carlton Gibson, 7 years ago

Triage Stage: Accepted → Ready for checkin

comment:5 by Tim Graham, 7 years ago

Patch needs improvement: set
Triage Stage: Ready for checkin → Accepted

comment:6 by Clifford Gama, 14 months ago

Cc: Clifford Gama added

comment:7 by Claude Paroz, 13 months ago

For the record, I'm still reading the same index size limitations on version 9: ​https://dev.mysql.com/doc/refman/9.0/en/innodb-limits.html

Note: See TracTickets for help on using tickets.
Back to Top