I'm running MySQL 5.0.41-community-nt on a Win32 machine. Each time I create a new table the table and field names are changed to lowercase!

I have already changed the MySQL directive lower_case_table_names to 0 in my.ini in my Windows directory and added the following line to the group [mysqld]:

set-variable = lower_case_table_names=0

Still, here's my complete my.ini file:

#This File was made using the WinMySQLAdmin 1.4 Tool
#6/22/2007 11:15:36 PM

#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions

[mysqld]
basedir=N:/xampp/mysql
#bind-address=22.23.13.1
datadir=N:/xampp/mysql/data
#language=N:/xampp/mysql/share/your language directory
#slow query log#=
#tmpdir#=
#port=3306
#set-variable=key_buffer=16M
set-variable=lower_case_table_names=0
[WinMySQLadmin]
Server=N:/xampp/mysql/bin/mysqld-nt.exe
user=root
password=passwd

Can anyone tell me the solution????

    have you restarted mysqld since making those changes?

      Yes, multiple times... Even the whole system!!!!

        I think you might do it without the set-variable part, but I'm no MySQL guru

          Done that already... nd restarted tooo

            Yes... I have been through the referenced doc on mysql.com already.
            I have also tried setting the variable value to 2 & restarted. It still shows up as 1 in phpMyAdmin & WinMyAdmin.

            And I am trying to set it to 0, because that is the configuration my provider offers me...

              The only thing I can think of then is that you're editing the wrong my.cnf file...

              You might want to give a go at posting this question under installation with all this data and see if you can get a better answer there. If it's not this then I'm stumped.

              btw, is your provider on linux / unix and you're on windows? If so, I'd highly recommend setting up a linux box to run your dev env on, so you can emulate your production environment.

                There's only one my.cnf file in C:\Windows...
                And moreover, I amediting it with WinMySQLAdmin, the MySQL admin tool that accompanies Xampp...

                  Can you edit any other values and have them show up in phpmyadmin?

                    No...
                    If that means that I am editing the wrong file, then where is the correct one located???

                      I don't know. Maybe there isn't one and mysql is using default values?

                      Maybe the permissions on that file are such that the mysql daemon can't read them.

                        So, where should I look out for a solution.
                        I posted this on mysql.com forums also, but there has been no reply!!!

                          you got me. I rely on the pgsql mailing lists for solving my postgresql problems. I'd look for someone who knows mysql well and can sit down with you to interactively troubleshoot this.

                            Is the MySQL server starting as an NT service?

                            If so, try doing this:

                            1. Stop the service (Control Panel -> Administrative Tools -> Services -> Right click on the MySQL service, click stop)

                            2. Open a command prompt (Start -> Run -> cmd)

                            3. Navigate to MySQL's 'bin' directory (e.x. cd "C:\Program Files\MySQL\MySQL Server 5.0\bin" )

                            4. Try starting the MySQL server and explicitly state the my.ini file's location:

                              mysqld-nt  --defaults-file=C:\Windows\my.ini

                            Leave that DOS window open, and try checking the values in phpMyAdmin again -- see if they've changed.

                            If they have, then we'll need to modify the parameters of the NT service... but I'll save that how-to until we decide that this is the problem.

                              Finally that worked!!! Thanx.
                              So, what's the problem.... Moreover, why I couldnot solve it with WinMySqlAdmin????

                                Not sure... I've had to do this same thing on my home computer. What we need to do is to alter the startup path for the MySQL service. To do this, we have to edit the registry. If I had a big caution sign, I'd insert it here... so just be aware that incorrectly editing your registry can do some pretty icky things! 😉 Anywho...

                                1. Stop the MySQL service and any other instances of the MySQL server you may have running

                                2. Open the Registry Editor (Start -> Run -> regedit)

                                3. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services[/b]

                                4. Find the MySQL key (note that I've installed the service as "MySQL" though I don't believe this is the default... it might be MySQL5 or something similar) and click on it

                                5. On the right side, you should see a registry value called ImagePath. Double-click on it

                                6. It probably says something like: 

                                  "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt" MySQL

                                  but you need to change it to:

                                  "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt" --defaults-file="C:\Program Files\MySQL\MySQL Server 5.0\my.ini" MySQL

                                  Note that you should use the correct path to your my.ini file - I've chosen to place mine in the MySQL directory simply because this keeps everything in one directory (I don't want to go hunting for various .ini files when I upgrade a product, be it MySQL, PHP, etc. etc.)

                                7. Press OK on the Edit String dialog and close the Registry Editor

                                8. Start the MySQL service

                                9. Verify that your non-default values from the my.ini file are properly being applied (via phpMyAdmin, for example)

                                  Thanx... that was really a ggeky problem & a geeky solution!!!😉

                                    Write a Reply...