Actions
Bug #57805
closed
SQL-ERROR: Specified key was too long
Start date:
2014-04-10
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
In the upgrade process from 6.0 to 6.2 I get this error
Update failed! SQL-ERROR: Specified key was too long; max key length is 1000 bytes Update database schema: Modify tables and fields ALTER TABLE sys_file_processedfile CHANGE identifier identifier varchar(512) default '';
Files
Updated by Markus Klein over 10 years ago
- Category set to Install Tool
- Status changed from New to Accepted
- Priority changed from Should have to Must have
- Target version set to next-patchlevel
Happens on upgrading from 6.x.
Updated by Markus Klein over 10 years ago
In 6.0 the identifier field has varchar(200).
The wizard tries to extend the field to varchar(512) which fails somehow.
I suspect the reason is the associated index with the same name.
Maybe it helps to remove the index first (manually in the DB) and let the wizard try the step again. It should then be able to extend the field and re-create the index automatically.
Updated by Oliver Hader over 10 years ago
- File forge_57805.png forge_57805.png added
The reason seems to be the processing order and the fact the the existing index is not limited. Thus, it should be:
- drop index (DROP KEY identifier)
- modify field (CHANGE identifier)
- create index (ADD KEY identifier)
Updated by Markus Klein over 10 years ago
That's what I wrote above. But do we have a chance to do that automatically?
Updated by Nicole Cordes over 10 years ago
- Status changed from Accepted to Resolved
This issue was solved with patch for http://forge.typo3.org/issues/57421
Updated by
Actions