Changes between Initial Version and Version 1 of Ticket #18392, comment 48


Ignore:
Timestamp:
06/28/21 10:33:21 (12 months ago)
Author:
lambdaq
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18392, comment 48

    initial v1  
    33https://github.com/django/django/pull/14563
    44
    5 Lots of stuff had changed since the issue was first open two years ago. My two cents:
     5Lots of stuff had changed since the issue was first open ''nine'' years ago. My two cents:
    66
    7 1. In 5.7, innodb indexes no longer limits the 767 bytes hardcap on utf8mb4 indexes.
    8 
     71. In v5.7, innodb indexes no longer limits the 767 bytes hardcap on utf8mb4 indexes.
     8https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-7.html#mysqld-5-7-7-feature
    99> When innodb_file_format is set to Barracuda, innodb_large_prefix=ON allows index key prefixes longer than 767 bytes (up to 3072 bytes) for tables that use a Compressed or Dynamic row format.
    1010
     
    1313
    1414https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-1.html#mysqld-8-0-1-charset
     15> Important Change: The default character set has changed from latin1 to utf8mb4. These system variables are affected:
    1516
    16 I guess Django's decision to hack MySQL's default settings to less supported utf8mb3 (aka the utf8) would be unwise. It was a proper compromise 9 years ago, but it will be a liability in the years to come.
     17
     18IMHO Django's decision to hack MySQL's default settings to less supported utf8mb3 (aka the utf8) would be unwise. Maybe it was a proper compromise ''9 years ago'', but it will be a liability in the years to come.
    1719
    1820Maybe at least we can add some notes to alarm the readers?
Back to Top