Bug #31470 ndb table with special characters in name are not discovered correctly
Submitted: 9 Oct 2007 7:36 Modified: 6 Nov 2007 9:06
Reporter: Tomas Ulin Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0-> OS:Any
Assigned to: Tomas Ulin CPU Architecture:Any

[9 Oct 2007 7:36] Tomas Ulin
see below

How to repeat:
(test for 5.1)

# ndb table with special characters in name
# are not discovered correctly
connection server1;
use test;
create table `test`.`t1$EX`
 (server_id int unsigned,
  master_server_id int unsigned,
  master_epoch bigint unsigned,
  count int unsigned,
  primary key(server_id, master_server_id,
              master_epoch, count))
  engine ndb;

# check that table shows up ok on both servers
# before bugfix table would not show up on server2
show tables like '%$%';
connection server2;
use test;
show tables like '%$%';

# check cleanup
# before bugfix drop table would fail
drop table `test`.`t1$EX`;
show tables like '%$%';

connection server1;
show tables like '%$%';
[9 Oct 2007 7:39] 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:


ChangeSet@1.2569, 2007-10-09 09:39:39+02:00, tomas@whalegate.ndb.mysql.com +3 -0
  Bug #31470 ndb table with special characters in name are not discovered correctly
[9 Oct 2007 7:44] Tomas Ulin
will not fix in 5.0

patch queued 5.1, CGE 6.2, CGE 6.3
[10 Oct 2007 8:11] Jon Stephens
Documented bugfix in mysql-5.1.22-ndb-6.2.7 changelog; left in PQ status.
[15 Oct 2007 17:38] Jon Stephens
Also documented in mysql-5.1.22-ndb-6.3.4 changelog; left in PQ status.
[5 Nov 2007 13:53] Bugs System
Pushed into 6.0.4-alpha
[5 Nov 2007 13:57] Bugs System
Pushed into 5.1.23-rc
[6 Nov 2007 9:06] Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at


Documented fix in 5.1.23 and 6.0.4 changelogs. Also noted the issue in Cluster Limitations section of Manual.