Bug #27988 Non-ASCII table name reported incorrectly in error message
Submitted: 20 Apr 2007 17:20 Modified: 31 Jul 2008 8:45
Reporter: Aleksey Karyakin Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Charsets Severity:S3 (Non-critical)
Version:5.0.37 OS:Windows (, Mac OS X)
Assigned to: Assigned Account CPU Architecture:Any

[20 Apr 2007 17:20] Aleksey Karyakin
Description:
See example.
The table in the example is created with a Russian letter. Table name should be converted to client's charset on display instead of printing raw UTF8 codes. 

How to repeat:
mysql> set names cp1251;
Query OK, 0 rows affected (0.01 sec)

mysql> use test;
Database changed

mysql> create table `а` (i int); -- note non-ASCII symbol
Query OK, 0 rows affected (0.05 sec)

mysql> create table `а` (i int); -- note non-ASCII symbol
ERROR 1050 (42S01): Table '┬а' already exists

--note the table name is incorrect
[20 Apr 2007 17:39] Sveta Smirnova
Thank you for the report.

Verified as described. Mac client is affected too.
[28 Apr 2007 10:30] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/25664

ChangeSet@1.2649, 2007-04-28 14:33:46+05:00, svoj@mysql.com +3 -0
  BUG#27988 - mysqld crashed when executing INSERT DELAYED
              on a BLACKHOLE table
  
  Using INSERT DELAYED on BLACKHOLE tables could lead to server
  crash.
  
  This happens because delayed thread wants to upgrade a lock,
  but BLACKHOLE tables do not have locks at all.
  
  This patch rejects attempts to use INSERT DELAYED on MERGE
  tables.
[28 Apr 2007 10:33] Sergey Vojtovich
Sorry, wrong bug no.
[31 Jul 2008 8:45] Alexander Barkov
This is a duplicate bug for:

http://bugs.mysql.com/bug.php?id=1406