| Bug #10271 | Parsing of database name in ORDER BY clause is NOT case-insensitive | ||
|---|---|---|---|
| Submitted: | 29 Apr 2005 18:20 | Modified: | 28 May 2013 10:55 |
| Reporter: | Le Nguyen | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | 4.1.11 | OS: | Windows (Windows XP SP2) |
| Assigned to: | CPU Architecture: | Any | |
[29 Apr 2005 18:20]
Le Nguyen
[1 May 2005 3:09]
Jorge del Conde
Hi, Can you please upload your table schema so that I can try and reproduce this bug ? Thanks!
[3 May 2005 15:28]
Le Nguyen
Hello Jorge, don't forget that I am a newbie to MySQL. Are you talking about the INFORMATION_SCHEMA table? Can you give me detailed steps on how to get that information to you? LN
[3 May 2005 15:31]
Le Nguyen
Just in case you meant the output of a SHOW CREATE TABLE, here it is: | Cust | CREATE TABLE `cust` ( `application_date` date default NULL, `credit_code` char(2) collate latin1_bin default NULL, `credit_limit` double default NULL, `credit_rating` int(11) default NULL, `cust_name` char(31) collate latin1_bin default NULL, `cust_num` int(11) NOT NULL default '0', `last_review_date` date default NULL, `ship_terms` char(21) collate latin1_bin default NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_bin LN
[25 May 2005 8:20]
Vasily Kishkin
Could you please to paste any sample values of this table. I tried to repeat on my values and all worked fine.
[25 Jun 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[28 May 2013 10:55]
Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.
