cen
07/18/2018, 10:13 PMwell. for MariaDB-server-10.1 we get this error @groob
2018/07/18 20:58:55 FAIL 20170306075207_UseUTF8MB.go (alter table file_integrity_monitoring_files: Error 1071: Specified key was too long; max key length is 767 bytes), quitting migration.
did some looking around
found this here
gogs/gogs#4894
Because of mysql 5.6 (includes prior versions) InnoDB max index length is 767 bytes, mysql 5.7.7 is up to 3072 bytes.
If some varchar column's length is 255, when the character format is utf-8 needs 2553=765 bytes for index length, It's OK.
But, an utf8mb needs 2554=1020 bytes for index length.
Solutions:
UPGRADE the mysql to 5.7.7(Mariadb 10.2.2)
Change the utf8mb column length to 191 (191*4=764)
Change the utf8mb to utf8
set innodb_file_format=Barracuda, innodb_large_prefix=on and create table using ROW_FORMAT=DYNAMIC or COMPRESSED (default for 5.7.7)
seems to be the same issue
groob
07/19/2018, 5:36 PMmarpaia
07/19/2018, 5:38 PMcen
07/19/2018, 5:38 PMgroob
07/19/2018, 5:38 PMcen
07/19/2018, 5:43 PMLatest release
marpaia
07/19/2018, 6:08 PMcen
07/19/2018, 6:17 PMLatest release
marpaia
07/19/2018, 6:19 PMcen
07/19/2018, 6:28 PMmarpaia
07/19/2018, 6:35 PMcen
07/19/2018, 6:41 PMredis(MeghaCache)sorry i ment Memcached
and can you update mariadbNo I can not
marpaia
07/19/2018, 6:42 PMcen
07/19/2018, 6:48 PMmarpaia
07/19/2018, 6:48 PM