[java] CREATE INDEX FXI_CD_ASS_FTEXT1024 ON FX_CONTENT_DATA(ASSIGN,FTEXT1024)
[java] Error setting up division: Specified key was too long; max key length is 1000 bytes
Description
[java] CREATE INDEX FXI_CD_ASS_FTEXT1024 ON FX_CONTENT_DATA(ASSIGN,FTEXT1024)
[java] Error setting up division: Specified key was too long; max key length is 1000 bytes
I was unable to reproduce this on other installations. A complete reinstall of MySQL fixed the problem, apparently something went wrong during the upgrade. It seems that MySQL applied the 1000 bytes restriction on the whole composite key, while InnoDB apparently allows longer keys (as long as the individual parts stay below 768 bytes).
Daniel Lichtenberger added a comment - 13/Jul/10 08:22 AM I was unable to reproduce this on other installations. A complete reinstall of MySQL fixed the problem, apparently something went wrong during the upgrade. It seems that MySQL applied the 1000 bytes restriction on the whole composite key, while InnoDB apparently allows longer keys (as long as the individual parts stay below 768 bytes).
![framework.[fleXive]™ Issuetracker](/jira/s/472/1/_/images/Logo_Flexive.gif){kind=logo}
Bug
Closed
Critical
MySQL: database setup fails on Ubuntu 10.04 (Specified key was too long)
I was unable to reproduce this on other installations. A complete reinstall of MySQL fixed the problem, apparently something went wrong during the upgrade. It seems that MySQL applied the 1000 bytes restriction on the whole composite key, while InnoDB apparently allows longer keys (as long as the individual parts stay below 768 bytes).