Page MenuHomePhabricator

[Comments] sql/comments.sql : Error: 1071 Specified key was too long; max key length is 767 bytes
Open, Needs TriagePublic

Description

When running MySQL/MariaDB with charset utf8mb4, a character is 4 bytes. Hence a key created on a VARCHAR(255) takes 255 characters * 4 bytes/characters = 1020 bytes. However Innodb defaults to a maximum of 767 bytes for an index.

The extension fails to install on Debian Stretch which uses utf8mb4 as the default charset:

Query: CREATE UNIQUE INDEX Comments_Vote_user_id_index ON `Comments_Vote` (Comment_Vote_ID,Comment_Vote_Username)

Function: Wikimedia\Rdbms\Database::sourceFile( /workspace/src/extensions/Comments/includes/../sql/comments.sql )
Error: 1071 Specified key was too long; max key length is 767 bytes (localhost:/tmp/quibble-mysql-egsudwcr/socket)

Event Timeline

hashar created this task.May 1 2018, 7:19 PM
hashar edited projects, added Comments; removed Release-Engineering-Team (Kanban), Quibble.
hashar removed a subscriber: gerritbot.
Restricted Application added a project: Social-Tools. · View Herald TranscriptMay 1 2018, 7:19 PM
Vvjjkkii renamed this task from [Comments] sql/comments.sql : Error: 1071 Specified key was too long; max key length is 767 bytes to 8udaaaaaaa.Jul 1 2018, 1:12 AM
Vvjjkkii triaged this task as High priority.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed a subscriber: Aklapper.
Mainframe98 renamed this task from 8udaaaaaaa to [Comments] sql/comments.sql : Error: 1071 Specified key was too long; max key length is 767 bytes.Jul 1 2018, 10:55 AM
Mainframe98 raised the priority of this task from High to Needs Triage.
Mainframe98 updated the task description. (Show Details)
Mainframe98 added a subscriber: Aklapper.