Re: MySql 5.7.3 m13 deadly slow - config issue?
Hi,
MySQL will not use index if a type conversion is needed. VARCHAR columns with different character set or collation is regarded as being of different type.
One reason for this is that two strings that may be considered equal with one collation may not be considered equal with another collation (e.g., case-sensitive versus case-insensitive). Hence, within an index, from the point of view of a different collation, all rows with matching strings may not be located together, and it will not be possible to use an index look-up to find matching rows.
I am not very familiar with what changes have been done to character sets over the years, so I am not able to tell why you see different behavior in MySQL 5.7 compared to an earlier version.
Øystein Grøvlen,
Senior Principal Software Engineer,
MySQL Group, Oracle,
Trondheim, Norway
Subject
Views
Written By
Posted
4617
January 13, 2014 06:21PM
1779
January 14, 2014 03:40AM
1467
January 14, 2014 12:24PM
Re: MySql 5.7.3 m13 deadly slow - config issue?
1805
January 15, 2014 04:38AM
1203
January 14, 2014 04:27PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.