Bug #3441 lower_case_table_names=2: MYI file is lowercased after a table is optimized
Submitted: 11 Apr 2004 23:08 Modified: 13 Apr 2004 8:12
Reporter: Sergei Kulakov (Candidate Quality Contributor) Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0.18 Windows source OS:Windows (Windows)
Assigned to: CPU Architecture:Any

[11 Apr 2004 23:08] Sergei Kulakov
A MyIsam table has 3 files with the extensions frm, MYD, MYI. If lower_case_table_names=2 the table is created with the case specified, and all 3 files has the same case. But if the table is then filled with some data and optimized, the index file MYI gets lowercased.

How to repeat:
1. create the table

CREATE TABLE AbC (i int, Index(i))

creates the 3 files AbC.frm, AbC.MYD, AbC.MYI

2. Fill it with data (optimize won't work without any data)

Insert Into AbC Values(1)

3. Optimize it

Optimize Table AbC

Now we have the 3 files AbC.frm, AbC.MYD and abc.MYI that is the index file got lowercased.

Suggested fix:
[12 Apr 2004 6:54] MySQL Verification Team
Thank you for the bug report I was able to repeat.
[13 Apr 2004 8:12] Guilhem Bichot
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 bugfix, yourself. More information 
about accessing the source trees is available at