Bug #35791 The NDB file on SQL Nodes may differ in cases from FRM file
Submitted: 3 Apr 2008 9:59 Modified: 3 Apr 2008 10:00
Reporter: Geert Vanderkelen Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1 OS:Mac OS X (10.5.2)
Assigned to: CPU Architecture:Any
Tags: 5.1.23
Triage: Triaged: D4 (Minor)

[3 Apr 2008 9:59] Geert Vanderkelen
Description:
Creating a table in Cluster with cases in the filename makes the .frm file OK, but the .ndb has wrong cases.

I have seen this only on Mac, since filesystem case sensitivity is important there. Maybe issue on Windows too?
On Linux, setting lower_case_table_names=2 doesn't reflect problems.

This probably will not cause to much problems since in systems with lower_case_table_names set, it will report that table already exists. But not retaining cases isn't fine either.

How to repeat:
(On Mac OS)

080403 11:44:37 [Warning] Setting lower_case_table_names=2 because file system for /var/mysql/ is case insensitive

mysql> show variables like '%case%';
+------------------------+-------+
| Variable_name          | Value |
+------------------------+-------+
| lower_case_file_system | ON    | 
| lower_case_table_names | 2     | 
+------------------------+-------+

mysql> CREATE TABLE UPPERCASED (id INT, c1 VARCHAR(20), PRIMARY KEY(id)) ENGINE=NDB;

On the file system it looks like:
-rw-rw----  1 _mysql  _mysql  8582 Apr  3 11:45 UPPERCASED.frm
-rw-rw----  1 _mysql  _mysql     0 Apr  3 11:45 uppercased.ndb
[3 Apr 2008 10:00] Geert Vanderkelen
Verified it works OK on Linux. On Mac OS 10.5 not.