Quote:
|
Originally Posted by Coleshadowblades
I said WINDOWS specific meaning everyone says "oh thats a windows only error" instead of actually fixing it they pawn it off on windows and just leave it be lol
|
I don't recall the exact fix, but this is probably due to the changes in how case is handled in table and field names that happen in MySQL 5. The Windows bit is due to Windows being ^&%*&%* about case handling in general.
There's a setting you can use in my.conf to use "old style" case handling for Windows machines. Look it up.
There's also new string handling functions that should be used, but I can't recall exactly what they are. Most people I know just don't let Windows try to be a server that runs MySQL....
Note that this is not intended to be a flame of any kind. But that's probably why you've got the error.