List:Commits« Previous MessageNext Message »
From:Chad MILLER Date:July 18 2007 7:42pm
Subject:Re: bk commit into 5.0 tree (cmiller:1.2503) BUG#26909
View as plain text  
On 18 Jul 2007, at 12:57, Ingo Strüwing wrote:

> Chad MILLER wrote:
> ...
>> ChangeSet@stripped, 2007-07-12 15:11:49-04:00,  
>> cmiller@stripped +3 -0
>>   Bug#26909: Specified key was too long; max key length is 255  
>> bytes \
>>   	when creating table
>>
>>   Federated tables have an artificially low maximum of key length,
>>   because the handler fails to implement a method to return it and
>>   the default value is taked from the prototype handler.
> ...
>> -  uint max_supported_key_length()    const { return  
>> MAX_KEY_LENGTH; }
>> +  uint max_supported_key_length()    const { return  
>> FEDERATED_MAX_KEY_LENGTH; }
>> +  uint max_supported_key_part_length() const { return  
>> FEDERATED_MAX_KEY_LENGTH; }
>
> Ok. Next time I will wait a week after being asked to review. Just to
> see if more changes come in.

Would that change anything here?  This changeset is from last  
Thursday.  - chad

--
Chad Miller, Software Developer                         chad@stripped
MySQL Inc., www.mysql.com
Orlando, Florida, USA                                13-20z,  UTC-0400
Office: +1 408 213 6740                         sip:6740@stripped



Attachment: [application/pgp-signature] This is a digitally signed message part PGP.sig
Thread
bk commit into 5.0 tree (cmiller:1.2503) BUG#26909Chad MILLER12 Jul
  • Re: bk commit into 5.0 tree (cmiller:1.2503) BUG#26909Ingo Strüwing18 Jul
    • Re: bk commit into 5.0 tree (cmiller:1.2503) BUG#26909Chad MILLER18 Jul
      • Re: bk commit into 5.0 tree (cmiller:1.2503) BUG#26909Ingo Strüwing19 Jul