-
Committer:
Stewart Smith
-
Author(s):
Magne Mahre, Stewart Smith
-
Date:
2010-12-03 03:49:04 UTC
-
mto:
(2021.1.2 build)
-
mto:
This revision was merged to the branch mainline in
revision
1986.
-
Revision ID:
stewart@flamingspork.com-20101203034904-snwcp5lps0nb2v53
Merge Revision revid:magne.mahre@sun.com-20100901173834-7lrqgycyuxsg4ab7 from MySQL InnoDB
Original revid:magne.mahre@sun.com-20100901173834-7lrqgycyuxsg4ab7
Original Authors: Magne Mahre <magne.mahre@sun.com>
Original commit message:
Bug#39932 "create table fails if column for FK is in different
case than in corr index".
Server was unable to find existing or explicitly created supporting
index for foreign key if corresponding statement clause used field
names in case different than one used in key specification and created
yet another supporting index.
In cases when name of constraint (and thus name of generated index)
was the same as name of existing/explicitly created index this led
to duplicate key name error.
The problem was that unlike all other code Key_part_spec::operator==()
compared field names in case sensitive fashion. As result routines
responsible for getting rid of redundant generated supporting indexes
for foreign key were not working properly for versions of field names
using different cases.
(backported from mysql-trunk)