Skip to content
New issue

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

Mentioned the 767 bytes index limit and its solution #10055

Closed
wants to merge 2 commits into from

Conversation

@javiereguiluz
Copy link
Member

@javiereguiluz javiereguiluz commented Jul 12, 2018

This fixes #6398. Sadly this error is very common (I also faced myself several times) and the error message is cryptic, so let's document this problem and its solution.

@javiereguiluz javiereguiluz added this to the 2.8 milestone Jul 12, 2018
javiereguiluz added a commit that referenced this pull request Jul 16, 2018
…viereguiluz)

This PR was squashed before being merged into the 2.8 branch (closes #10055).

Discussion
----------

Mentioned the 767 bytes index limit and its solution

This fixes #6398. Sadly this error is very common (I also faced myself several times) and the error message is cryptic, so let's document this problem and its solution.

Commits
-------

092b7c0 Mentioned the 767 bytes index limit and its solution
@lyrixx
Copy link
Member

@lyrixx lyrixx commented Nov 13, 2018

thanks @javiereguiluz for this doc entry.

I think we could also talk about about barracuda. We are using this configuration to solve this issue:

[mysqld]
innodb_large_prefix=on
innodb_file_format=barracuda
innodb_file_per_table=true

ping @damienalexandre

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.