dwarf03 Posted June 15, 2018 Group: Members Topic Count: 2 Topics Per Day: 0.00 Content Count: 14 Reputation: 0 Joined: 02/27/12 Last Seen: June 27, 2018 Share Posted June 15, 2018 Hello. I'm using MySQL Workbench and this error appears. I don't know whats wrong. Can you guys help me? It's my first time and I am a beginner to this. Thank you so much in advance. Quote Link to comment Share on other sites More sharing options...
0 Tyrfing Posted June 15, 2018 Group: Members Topic Count: 0 Topics Per Day: 0 Content Count: 86 Reputation: 21 Joined: 10/02/13 Last Seen: October 23, 2024 Share Posted June 15, 2018 (edited) In MySQL version 5.7 and upwards this limit has been increased to 3072 bytes. https://stackoverflow.com/a/36405914 So, make sure you are using MySQL 5.7. Edited June 15, 2018 by Tyrfing Quote Link to comment Share on other sites More sharing options...
0 dwarf03 Posted June 15, 2018 Group: Members Topic Count: 2 Topics Per Day: 0.00 Content Count: 14 Reputation: 0 Joined: 02/27/12 Last Seen: June 27, 2018 Author Share Posted June 15, 2018 1 minute ago, Tyrfing said: 767 bytes is the stated prefix limitationfor InnoDB tables in MySQL version 5.6 (and prior versions). It's 1,000 bytes long for MyISAM tables. In MySQL version 5.7 and upwards this limit has been increased to 3072 bytes. So, make sure you are using MyISAM tables or MySQL 5.7. Hello sir Tyrfing good day. I'm not so sure about what you are asking but can you tell me if this is right? Quote Link to comment Share on other sites More sharing options...
0 dwarf03 Posted June 15, 2018 Group: Members Topic Count: 2 Topics Per Day: 0.00 Content Count: 14 Reputation: 0 Joined: 02/27/12 Last Seen: June 27, 2018 Author Share Posted June 15, 2018 Oh, you had edited your reply. Okay let me try to downgrade, mine will update you sooner if it works! Thank you! 8 minutes ago, Tyrfing said: In MySQL version 5.7 and upwards this limit has been increased to 3072 bytes. https://stackoverflow.com/a/36405914 So, make sure you are using MySQL 5.7. Quote Link to comment Share on other sites More sharing options...
0 Tyrfing Posted June 15, 2018 Group: Members Topic Count: 0 Topics Per Day: 0 Content Count: 86 Reputation: 21 Joined: 10/02/13 Last Seen: October 23, 2024 Share Posted June 15, 2018 (edited) Sorry, you don't have to downgrade. I thought you were using 5.6. You need to Switch from innodb to myisam before importing your SQL files. Or change the collation to some other type. Try utf8_general_ci. Please refer to this link 23 minutes ago, Tyrfing said: Quote Edited June 15, 2018 by Tyrfing 1 Quote Link to comment Share on other sites More sharing options...
0 dwarf03 Posted June 15, 2018 Group: Members Topic Count: 2 Topics Per Day: 0.00 Content Count: 14 Reputation: 0 Joined: 02/27/12 Last Seen: June 27, 2018 Author Share Posted June 15, 2018 On 6/16/2018 at 7:35 AM, Tyrfing said: Sorry, you don't have to downgrade. I thought you were using 5.6. You need to Switch from innodb tô myisam before importing your SQL files. Please refer to this link Still not getting the point I'm sorry hehe. Hold on. Finally!!!! Thank you so much! Quote Link to comment Share on other sites More sharing options...
Question
dwarf03
Hello. I'm using MySQL Workbench and this error appears. I don't know whats wrong. Can you guys help me? It's my first time and I am a beginner to this. Thank you so much in advance.
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.