Bug #57805
closed
SQL-ERROR: Specified key was too long
Added by Ben van 't Ende over 10 years ago.
Updated about 6 years ago.
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
- 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.
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.
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)
That's what I wrote above. But do we have a chance to do that automatically?
- Status changed from Accepted to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by