You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While installing, database migrations fail with the following error:
Mysql2::Error: Index column size too large. The maximum column size is 767 bytes.: CREATE INDEX index_remote_repo_revisions_on_remote_repo_id_and_sha ON remote_repo_revisions (remote_repo_id, sha)
A quick and dirty workaround is to run the following command in MySQL, which will make it silently ignore the error and truncate the length of the index name:
set GLOBAL innodb_large_prefix=OFF;
You can re-enable it after executing the migration.
The text was updated successfully, but these errors were encountered:
jmfarina
changed the title
Index name too long
Index column size too large
Sep 18, 2016
While installing, database migrations fail with the following error:
Mysql2::Error: Index column size too large. The maximum column size is 767 bytes.: CREATE INDEX
index_remote_repo_revisions_on_remote_repo_id_and_sha
ONremote_repo_revisions
(remote_repo_id
,sha
)A quick and dirty workaround is to run the following command in MySQL, which will make it silently ignore the error and truncate the length of the index name:
set GLOBAL innodb_large_prefix=OFF;
You can re-enable it after executing the migration.
The text was updated successfully, but these errors were encountered: