Changes between Initial Version and Version 1 of Ticket #31144


Ignore:
Timestamp:
Jan 8, 2020, 7:38:03 AM (5 years ago)
Author:
Steven Mapes
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #31144 – Description

    initial v1  
    11There is a bug within db.backends.mysql.validation.check_field_type where the maximum unique constraints is still being limited to 255 characters even though MySQL supports unique keys of up to 1000 characters by default and InnoDB supports 3072 bytes for InnoDB tables that use DYNAMIC or COMPRESSED row format and 767 bytes for InnoDB tables that use the REDUNDANT or COMPACT row format.
    22
     3MySQL supports VARCHARs of up to 65,535 length. It's only CHAR that is restricted to 255 and as Django creates VARVCHARs there is no need to enforce that limit.
     4
    35Reference  -
    4 InnoDB - https://dev.mysql.com/doc/refman/8.0/en/innodb-limits.html
    5 
    6 MyISAM - https://dev.mysql.com/doc/refman/8.0/en/myisam-storage-engine.html
     61. InnoDB - https://dev.mysql.com/doc/refman/8.0/en/innodb-limits.html
     72. MyISAM - https://dev.mysql.com/doc/refman/8.0/en/myisam-storage-engine.html
     83. CHAR and VARCHAR Types -https://dev.mysql.com/doc/refman/8.0/en/char.html
    79
    810Example
    … …  
    2325
    2426It just needs the max length to be increased on line 38 of db.backends.mysql.validation
     27
     28This is across all branches
Back to Top