Your message dated Mon, 21 Sep 2020 22:28:57 +0300 with message-id <CAHj_TLBi92fB+GJEv=nmvkeonwxj+3r6+ma2wljdyugszwg...@mail.gmail.com> and subject line Re: Bug#848603: Enable innodb_large_prefix has caused the Debian Bug report #848603, regarding Enable innodb_large_prefix to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 848603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848603 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mariadb-server Version: 10.0.28-2 Severity: serious mariadb-server, the new default-mysql-server, breaks existing well-functioning applications that need to index columns defined as VARCHAR(255). This worked fine with mysql-server-5.6. This is caused by two questionable choices: * default character set is utf8mb4 (causing index prefix lengths quadruple). * innodb_large_prefix is OFF. I'd suggest you enable innodb_large_prefix or revert to what mysql-server-5.6 did, i.e. set the character set to utf8 (which uses "just" 3 bytes per character). Thanks, -- christian hofstaedtler <[email protected]>
--- End Message ---
--- Begin Message ---Version: 1:10.1.34-1 The configs innodb_large_prefix=on innodb_default_row_format=dynamic have been backported to MariaDB 10.1 since 2018 and enabled by default, which should have fixed this issue.
--- End Message ---
