Bug #56786

Index on sys_file_processedfile is too large

Added by Ernesto Baschny over 7 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Should have
Category:
File Abstraction Layer (FAL)
Target version:
Start date:
2014-03-11
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:

Description

Since #54234 a SQL error in the Upgrade Wizard / Database Compare is left open:

ALTER TABLE sys_file_processedfile ADD KEY identifier (storage,identifier); 
Specified key was too long; max key length is 1000 bytes

"identifier" is varchar(512) but on utf8 charset every character needs 3 bytes of space. So the index is "too large" (for MyISAM).

Solution would be to limit the key to the first 332 chars.


Related issues

Related to TYPO3 Core - Task #54234: Prevent creation of FileObjects for ProcessedFilesClosedSteffen Ritter2013-12-06

Actions
Related to TYPO3 Core - Bug #57805: SQL-ERROR: Specified key was too longClosed2014-04-10

Actions
Has duplicate TYPO3 Core - Bug #57002: SQL-Errors while Upgrading the database with Upgrade WizardClosed2014-03-17

Actions
#1

Updated by Gerrit Code Review over 7 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/28272

#2

Updated by Gerrit Code Review over 7 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/28272

#3

Updated by Ernesto Baschny over 7 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#4

Updated by Gerrit Code Review about 7 years ago

  • Status changed from Resolved to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/28429

#5

Updated by Ernesto Baschny about 7 years ago

  • Status changed from Under Review to Resolved
#6

Updated by Riccardo De Contardi over 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF