schnuckelg Posted March 24, 2017 Share Posted March 24, 2017 during installation of Version 1.7 I got following error: SQL error on query Specified key was too long; max key length is 1000 bytes I guess it could be that Prestashop 1.7 is developed for mysql 5.7 (where indexes could be little bit more than 3072 Bytes but the only installation requirement that i have found is mysql 5 and up. Is that right? Link to comment Share on other sites More sharing options...
bellini13 Posted March 24, 2017 Share Posted March 24, 2017 the database collation setting also effects the key length. I typically use utf8_general_ci and do not have issues with key lengths. I use earlier versions of mysql (not 5.7) as well you could also try to reduce the column length of the columns in question, which are likely defined as varchar(255) and probably do not need to be so long. Link to comment Share on other sites More sharing options...
Amit Sarode Posted January 12, 2019 Share Posted January 12, 2019 Hi, Specified key was too long; max key length is 1000 bytes Just change the table engine from MyIsam to InnoDB thru phpmyadmin -->Operations. Go to table structure first.. 2 Link to comment Share on other sites More sharing options...
CristianMoi Posted January 23, 2020 Share Posted January 23, 2020 On 1/12/2019 at 5:16 PM, Amit Sarode said: Hi, Specified key was too long; max key length is 1000 bytes Just change the table engine from MyIsam to InnoDB thru phpmyadmin -->Operations. Go to table structure first.. Thanks for this answer, I had this problem and I didn't know how to solve it. Link to comment Share on other sites More sharing options...
Galinowski Posted September 7, 2022 Share Posted September 7, 2022 It's an old post but it helped me to solve a problem while upgrading "Specified key was too long; max key length is 1000 bytes" for 4 tables in the logs. I changed from mariaDB to innoDB for each table involved by going to phpmyadmin, selecting the table, clicking on operations, then using the "storage engine" dropdown, Go. I ran the upgrade again and got <action result="error" id="28"/> but also "You already have the 1.7.8.7 version." in the logs, so it all seems good now! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now