Bug #9907 | full text search in boolean mode becoming case sensitive | ||
---|---|---|---|
Submitted: | 14 Apr 2005 14:55 | Modified: | 12 May 2005 20:37 |
Reporter: | Matthew Lord | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.1.11 | OS: | Any (all) |
Assigned to: | Alexander Barkov | CPU Architecture: | Any |
[14 Apr 2005 14:55]
Matthew Lord
[14 Apr 2005 15:00]
Matthew Lord
Could we do one of these things: 1) autoconvert the non char column 2) produce an error that a non char column is in match clause 3) produce a warning that states the non char column in match clause is causing case sensitivity.
[14 Apr 2005 18:02]
Sergei Golubchik
we do 1) already - a number is converted to a string. And when a number is converted to a string the result has 'binary' charset. Thus the whole expression is converted to a binary charset - and comparison becomes case-sensitive. The fix would be to use not to assign binary charset to a number converted to a string.
[10 May 2005 12:05]
Alexander Barkov
After discussion with PeterG, Monty and Sergey, we decided that number-to-string conversion will be change in 5.1. We won;t fix this bug before 5.1.
[12 May 2005 20:37]
Sergei Golubchik
Actually, this is not a bug. The behaviour is correct - implicit number to string conversion results in a string that has "binary" character set, concatenating "binary" and another character set yields binary. In 5.1 we'll change the charset of the implicit number to string conversion and it'll "fix" this issue too.