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

Danny Robert (JIRA) jira at osuosl.org
Wed Feb 1 18:04:01 PST 2006


     [ http://bugs.osuosl.org/browse/MNT-1405?page=comments#action_10771 ]
     
Danny Robert commented on MNT-1405:
-----------------------------------

I (Danny) do not know that much about database storage, but what does a key like the one given in the report gain us?  Seems like every column in this table is part of some key or another.

Additional work will have to be done to test the other columns...might not kill us to go through our schema and re-work our keys to something sensible if necessary.

Note:  Every change to the DB schema MUST be reflected in the update/upgrade scripts!

> 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, 2.6
>  Environment: MySQL 4.1+ with UTF-8 Encoding
>     Reporter: Danny Robert
>     Assignee: Michael Clay
>      Fix For: 2.6

>
>
> 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:
   http://bugs.osuosl.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



More information about the Maintain-dev mailing list