convert to utf8mb4_unicode_ci collation fails on users table

Closed
Advanced Security - PHP Register/Login System Advanced Security - PHP Register/Login System October 21, 2018
Login to reply
Milos Stojanovic Support Agent
11 months ago

Hey Tom,

Ok, awesome! Glad to hear that. :)

Regards,
Milos

tom cloud
11 months ago

Conversion to MyISAM engine (to solve the index key problem) and utf8mb4_unicode_ci collation went okay

Milos Stojanovic Support Agent
11 months ago

Hey Tom,

Yes, you can convert it to MyISAM if you want to. Thanks for the suggestion, I'll update it for the future releases.

Regards,
Milos

tom cloud
11 months ago

I want to convert to DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci

but get error "specified key was too long; max key length is 767 bytes"

Would it be okay to set "ENGINE=MyISAM" rather than "ENGINE=InnoDB" ?? -- this would remove the problem of the key being too long, but I'm not sure if you're using features specific to InnoDB

Also -- maybe you could change your install script "stubs/as.sql" to use a more recent COLLATION than utf8_unicode_ci

for example: ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

thanks