[Maintain-dev] [JIRA] Resolved: (MNT-1405) MySQL Key size too large

Frederic Wenzel (JIRA) jira at osuosl.org
Tue Jun 20 10:56:51 PDT 2006

     [ http://bugs.osuosl.org/browse/MNT-1405?page=history ]
Frederic Wenzel resolved MNT-1405:

    Resolution: Fixed

Fixed in svn r4479. I replaced the ha index in the install and upgrade sql file by a smaller one. The big index was probably not productively used anywhere anyway.

In case we see performance dropping on big databases, we have to investigate indexes more closely.

> MySQL Key size too large
> ------------------------
>          Key: MNT-1405
>          URL: http://bugs.osuosl.org/browse/MNT-1405
>      Project: Maintain
>         Type: Bug
>   Components: Database
>     Versions: 2.4.0, 3.0
>  Environment: MySQL 4.1+ with UTF-8 Encoding
>     Reporter: Danny Robert
>     Assignee: Frederic Wenzel
>      Fix For: 3.0

> The MySQL schema used in Maintain is invalid when the default tables are UTF-8 encoded.  Since UTF-8 characters can be up to three bytes, the 1000-byte key limit is reached much more quickly.  From an IRC conversation:
> maintain.sql:  line 115: #1071 - Specified key was too long; max key length is 1000 bytes
> This is from the HOST table import, most likely due to this key:
> KEY `ha` (`ha`,`os`,`serial`,`last_seen`,`other_id`)
> Other keys should be checked as well.
> A temporary "solution" for this bug is to tell users to use latin encoding.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

More information about the Maintain-dev mailing list