| Bug #7617 | Incorrect lettercase-handling on ENUM-types | ||
|---|---|---|---|
| Submitted: | 2 Jan 2005 14:12 | Modified: | 22 Feb 2005 21:53 |
| Reporter: | Hajo Noerenberg | ||
| Status: | Closed | ||
| Category: | Server | Severity: | S3 (Non-critical) |
| Version: | 4.1.8 | OS: | Linux (Debian GNU/Linux 3.0) |
| Assigned to: | Jim Winstead | Target Version: | |
[2 Jan 2005 14:12]
Hajo Noerenberg
[2 Jan 2005 14:57]
Miguel Solorzano
Tested with latest BK source 4.1. Notice the warnings: mysql> update user set Reload_priv='y' where user="miguel"; Query OK, 1 row affected, 1 warning (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 1 mysql> show warnings; +---------+------+--------------------------------------------------+ | Level | Code | Message | +---------+------+--------------------------------------------------+ | Warning | 1265 | Data truncated for column 'Reload_priv' at row 5 | +---------+------+--------------------------------------------------+ 1 row in set (0.00 sec) Thank you for the bug report.
[11 Feb 2005 5:31]
Jim Winstead
The manual is incorrect to say that enum fields are always case-insensitive, as that actually depends on the collation specified for the enum field. (The same is true for set fields.) The bug here is that the enum and set columns in the privilege tables were set to a case-sensitive collation, and they should be case-insensitive to avoid this sort of confusion.
[18 Feb 2005 1:02]
Jim Winstead
Pushed, will be in 4.1.11.
[22 Feb 2005 21:53]
Paul DuBois
Noted in 4.1.11 changelog. Also updated the ENUM and SET column sections to point out that they aren't necessarily case-insensitive any more.
