Page MenuHomePhabricator

[ConfirmAccount] backend/schema/mysql/ConfirmAccount.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 acr_name ON `account_requests` (acr_name)

Function: Wikimedia\Rdbms\Database::sourceFile( /workspace/src/extensions/ConfirmAccount/backend/schema/mysql/ConfirmAccount.sql )
Error: 1071 Specified key was too long; max key length is 767 bytes (localhost:/tmp/quibble-mysql-8hjkpc_4/socket)

Event Timeline

hashar created this task.May 1 2018, 7:20 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 1 2018, 7:20 PM
Vvjjkkii renamed this task from [ConfirmAccount] backend/schema/mysql/ConfirmAccount.sql : Error: 1071 Specified key was too long; max key length is 767 bytes to 7udaaaaaaa.Jul 1 2018, 1:12 AM
Vvjjkkii triaged this task as High priority.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed subscribers: gerritbot, Aklapper.
Mainframe98 renamed this task from 7udaaaaaaa to [ConfirmAccount] backend/schema/mysql/ConfirmAccount.sql : Error: 1071 Specified key was too long; max key length is 767 bytes.Jul 1 2018, 11:38 AM
Mainframe98 raised the priority of this task from High to Needs Triage.
Mainframe98 updated the task description. (Show Details)
Mainframe98 added subscribers: gerritbot, Aklapper.