We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If use mysql innaDB, and utf8_mb4, cause (1071, 'Specified key was too long; max key length is 767 bytes')
The text was updated successfully, but these errors were encountered:
Odd, the hostname has a max_length of 250. What port did you use? Did it had 5 digits? Does it work with 4 digits?
max_length
Sorry, something went wrong.
It crash when you migration/build the table. the error is throwed by MySQL. I think it not allow unique_together too long when use utf8_mb4
What data do you have in your redisboard_server table?
Thanks, -- Ionel Cristian Mărieș, http://blog.ionelmc.ro
On Fri, Aug 7, 2015 at 1:48 PM, NY [email protected] wrote:
It crash when you migration/build the table. the error is throwed by MySQL. I think it not allow unique_together too long when use utf8_mb4 — Reply to this email directly or view it on GitHub #17 (comment) .
— Reply to this email directly or view it on GitHub #17 (comment) .
I not save any data. because there is no table. It just crash when migraion.
No branches or pull requests
If use mysql innaDB, and utf8_mb4, cause (1071, 'Specified key was too long; max key length is 767 bytes')
The text was updated successfully, but these errors were encountered: