see the problem is, i was designing a site on my local server, then when I ftp'd the site to a remote server to be on the web, i had database issues. There is a variable in phpmyadmin called, "lower_case_table_names and by default is = "1" when dealing with windows. My remote server is UNIX and unix is =0 by default. 1 means the the tables are not case sensitive, on the other hand 0 means that the tables in sql are case sensitive.

For some reason, sql tables are always in lower case letters. So when the code checks the tables, I get a database error because my variable lower_case_table_names = 0 when it should be a 1. I talked to my host and the techs hardly ever know whats going on. Seems like I school them and they suppose to be the experts. I don't know whats going on with servers, apache, sql and all that stuff, they suppose to know that. They told me that it was global and if it was changed, it would effect everybody elses site that is on that shared server.

Thats why I need to know how to either change the variable, and I tried "SET lower_case_table_names=1," didn't work. So I need to know how to change the variable or see the original names of my tables so that I could create all the tables to what the program calls them, and call it a day.

I need a database guru to haelp with this one, is there one out there? I have version 5.2 something as far as mysql.

Thanks jb

  • Apologies, but have you tried asking this question on Stack Overflow? DB / server-side questions tend to fare better there. Not saying there aren't any db experts here of course... I've never come accross this problem before, I have Apache setup on my home windows computer and afaik my hosts use UNIX, when I've uploaded db code it's always been fine... danwellman over 8 years ago

1 answer


Unfortunately, a shared host is not going to change mysql settings just for you. A change of that level could possibly affect hundreds of their clients using the same DB server. You can generally overrule web side stuff with a cgi-script, an htaccess file, or a custom .ini file. With DB stuff you may want to look into hopping on a VPS for your DB stuff but stay on shared hosting for your webhost.

Answered over 8 years ago by Tallboy