[TYPO3-english] realURL: update error: Specified key was too long; max key length is 1000 bytes

[Daniel Doesburg]

Hi Jigal,

It's a pity, I was not so successful.
First I removed the key. The file compare says tried to rebuild the key, 
without results. The same error message.

I totaly removed realurl and reinstalled. Now the table 
"tx_realurl_uniqalias" can not be created for the same reason.

I think, it's time for the bug tracker.


Best regards,

Daniel Doesburg



Op 13-9-2010 11:26, Jigal van Hemert schreef:
> Hi Daniel,
>
> On 13-9-2010 9:23, Daniel Doesburg wrote:
>> ERROR Specified key was too long; max key length is 1000 bytes
>>
>> lastBuiltQuery
>> ALTER TABLE tx_realurl_uniqalias CHANGE tablename tablename varchar(255)
>> default '';
>
> In your dump it shows that the index 'bk_realurl02' contains the entire
> column 'tablename'.
>
> Usually the strategy of TYPO3 to first create/change the columns and
> then create/change the indexes (keys) works fine. In this case the key
> would become too large and the column can't be changed.
>
> It would be enough to temporarily drop the key (TYPO3 will recreate it
> for you):
>
> ALTER TABLE tx_realurl_uniqalias DROP KEY bk_realurl02;
>
> (Or delete this index in phpMyAdmin)
>
> Then you can safely update the Realurl tables. If the index is still
> needed by RealUrl the index will be re-created.
>