Project

General

Profile

Actions

Bug #105515

open

Database update failed: Specified key was too long; max key length is 1000 bytes

Added by Frank Nägler 1 day ago. Updated 1 day ago.

Status:
Accepted
Priority:
Must have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
Start date:
2024-10-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
13
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

See screenshot below:

The table is of type MyISAM.

Key is UNIQUE KEY entry_identifier (entry_namespace,entry_key)
Both fields are varchar(128) and with the change from utf8mb3 to utf8mb4 this is now: (128 + 128) * 4 = 1024

The core fails to update the table to InnoDB.


Files


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #104153: About "row size too large"Closed2024-06-19

Actions
Actions #1

Updated by Benjamin Franzke 1 day ago

  • Status changed from New to Accepted
Actions #2

Updated by Benjamin Franzke 1 day ago

Actions #3

Updated by Benjamin Franzke 1 day ago

We should add an upgrade wizard (or integrate as forced default into Database Analyzer) to migrate all tables to InnoDB,
as it turns out that our schema relies on that (we default to utf8mb4 in new installations and use key length that are not allowed with MyISAM).

…and then we should update sections like
https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.2/Important-104153-AboutDatabaseErrorRowSizeTooLarge.html#ensure-storage-engine-is-innodb
to be informative only and mention that this is auto-updated and has not to be checked manually by an integrator (less things to do manually, that'd be good!)

Actions

Also available in: Atom PDF