SQL-ERROR: Specified key was too long
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 '';
Updated by Markus Klein over 6 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 6 years ago
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)