![3.0.6 upgrade to 3.1.2, run error: ER_TOO_LONG_KEY: Specified key was too long; max key length is 767 bytes · Issue #7273 · strapi/strapi · GitHub 3.0.6 upgrade to 3.1.2, run error: ER_TOO_LONG_KEY: Specified key was too long; max key length is 767 bytes · Issue #7273 · strapi/strapi · GitHub](https://user-images.githubusercontent.com/49556560/89002914-e7426300-d330-11ea-9469-46719077fcff.png)
3.0.6 upgrade to 3.1.2, run error: ER_TOO_LONG_KEY: Specified key was too long; max key length is 767 bytes · Issue #7273 · strapi/strapi · GitHub
![MySQL: ERROR 1071 (42000) at line: Specified key was too long; max key length is 767 bytes | by Needone App | Medium MySQL: ERROR 1071 (42000) at line: Specified key was too long; max key length is 767 bytes | by Needone App | Medium](https://miro.medium.com/v2/resize:fit:468/0*It91csFgdiHR2eQB.jpg)
MySQL: ERROR 1071 (42000) at line: Specified key was too long; max key length is 767 bytes | by Needone App | Medium
![mysql - 从mysql 7 导入到老版本的mysql6的报错:ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes - 申思维的技术站点-ruby/rails/titanium/敏捷方法论/测试驱动/自动化/全栈攻城狮/jquery/极客/直男 mysql - 从mysql 7 导入到老版本的mysql6的报错:ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes - 申思维的技术站点-ruby/rails/titanium/敏捷方法论/测试驱动/自动化/全栈攻城狮/jquery/极客/直男](https://files.sweetysoft.com/blog_images/from_paste_20220522_155116.png)
mysql - 从mysql 7 导入到老版本的mysql6的报错:ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes - 申思维的技术站点-ruby/rails/titanium/敏捷方法论/测试驱动/自动化/全栈攻城狮/jquery/极客/直男
![Laravel Syntax error or access violation: 1071 Specified key was too long; max key length is 767 | DerekBliss.com Laravel Syntax error or access violation: 1071 Specified key was too long; max key length is 767 | DerekBliss.com](https://derekbliss.com/storage/posts/April2017/3vTyjQUjbmASMVi74OEx.png)
Laravel Syntax error or access violation: 1071 Specified key was too long; max key length is 767 | DerekBliss.com
![Update von 15.0.7 auf 16.0.0 funktioniert nicht: 1071 Specified key was too long; max key length is 767 bytes - 🇩🇪 Deutsch (german) - Nextcloud community Update von 15.0.7 auf 16.0.0 funktioniert nicht: 1071 Specified key was too long; max key length is 767 bytes - 🇩🇪 Deutsch (german) - Nextcloud community](https://help.nextcloud.com/uploads/default/optimized/2X/2/29c46974a4dfc39279f6667899837e4d6ed102e7_2_200x500.png)
Update von 15.0.7 auf 16.0.0 funktioniert nicht: 1071 Specified key was too long; max key length is 767 bytes - 🇩🇪 Deutsch (german) - Nextcloud community
![mysql - Laravel Migration Error: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes - Stack Overflow mysql - Laravel Migration Error: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes - Stack Overflow](https://i.stack.imgur.com/9GFCx.png)
mysql - Laravel Migration Error: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes - Stack Overflow
![Migrate issue on linuxserver/mariad container: "'Specified key was too long; max key length is 767 bytes" - General - Docker Community Forums Migrate issue on linuxserver/mariad container: "'Specified key was too long; max key length is 767 bytes" - General - Docker Community Forums](https://global.discourse-cdn.com/docker/original/3X/8/3/83b0ecce5fee8d08f857edec6d93cdc9ca36725f.png)
Migrate issue on linuxserver/mariad container: "'Specified key was too long; max key length is 767 bytes" - General - Docker Community Forums
![What do I do if the "Specified key was too long; max key length is 767 bytes" error message is displayed when I create indexes in an ApsaraDB RDS for MySQL instance? - What do I do if the "Specified key was too long; max key length is 767 bytes" error message is displayed when I create indexes in an ApsaraDB RDS for MySQL instance? -](https://help-static-aliyun-doc.aliyuncs.com/assets/img/en-US/4007819661/p515054.png)
What do I do if the "Specified key was too long; max key length is 767 bytes" error message is displayed when I create indexes in an ApsaraDB RDS for MySQL instance? -
![What do I do if the "Specified key was too long; max key length is 767 bytes" error message is displayed when I create indexes in an ApsaraDB RDS for MySQL instance? - What do I do if the "Specified key was too long; max key length is 767 bytes" error message is displayed when I create indexes in an ApsaraDB RDS for MySQL instance? -](https://help-static-aliyun-doc.aliyuncs.com/assets/img/en-US/1255575851/p44664.png)
What do I do if the "Specified key was too long; max key length is 767 bytes" error message is displayed when I create indexes in an ApsaraDB RDS for MySQL instance? -
![Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes - YouTube Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes - YouTube](https://i.ytimg.com/vi/ApS0yL_aXp4/mqdefault.jpg)
Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes - YouTube
![What do I do if the "Specified key was too long; max key length is 767 bytes" error message is displayed when I create indexes in an ApsaraDB RDS for MySQL instance? - What do I do if the "Specified key was too long; max key length is 767 bytes" error message is displayed when I create indexes in an ApsaraDB RDS for MySQL instance? -](https://help-static-aliyun-doc.aliyuncs.com/assets/img/en-US/4007819661/p515055.png)