[RESOLVED] Commenting Code in MySQL after Upgrade

jenni

Normally, when I have a comment that I want within a query, I use a #. But, we recently upgraded MySQL on our test server (I believe it is now 4.0.22?) and now every query with a # totally wonks out. Does anyone know if there is a mysql configuration setting that will make this work again?

If I wasn't dealing with code that had references to hexidecimal values (starting with #) I could just grep the server and manually remove all instances where I used this method for comments. As it is, there is way too much code and I don't want to risk missing a little #.

Any thoughts?

cheese

Hi Jenni,

As nobody else has given a suggestion on this one I will offer a possible answer.

How about a text editor and replace \n # with \n // (where \n is a new line).

If it is on a windows box you could use Ultra Edit and use the Replace in Files option.

MAKE SURE YOU BACK UP EVERYTHING BEFORE YOU TRY THIS !!!!!

Just a thought,

Neil.

jenni

That just might work! I won't do an automatic find and replace, but I think it will get me on the road to finding all of them so I can replace them manually. I'll also search for those with spaces before the #. You rock! Thank you so much for the idea.

Another quick question...What is the proper way to comment an SQL query? Is it a double dash?

cheese

Hi Jenni,

// for a signle line

/ blah blah
blah blah / for more than one line

Cheers,

Neil.

PS.... As long as you do a back up of all your files an Auto find and replace in all files is worth a try........

jenni

So the same commenting will work for MySQL as works for PHP? I didn't know that...Thanks.

jenni

This problem is funkier than I thought. I really have no clue what the deal is.

Here's where it stands:
- I have files that work perfectly on our production server, but error out on our test server.

Without question, the issue is any kind of commenting (# or --) in the mysql query. (Queries run fine until I add a comment.)
The queries with comments run fine when I paste them into phpMyAdmin.

Can anyone think of anything that I should look for in the PHP config or mySQL config? This is driving me bonkers!

cheese

Ah, have you got the error reporting set the same on both machines. Have a look in the php.ini file at this bit, about 1/3 the way down the file;

error_reporting = E_ALL
display_errors = On
display_startup_errors = On

These bits will give different error messages, if not set the same.

Might be the problem.

Cheers,

Neil.

jenni

It isn't php that is erroring out though. It is a mysql syntax error. That's what I don't get...

cheese

Have a look on my profile and send me the code, I will see if it works here and if it doesn't I can play with it, if you like.

Neil.

jenni

Unfortunately, I don't think that sending the code would help because it works fine on the production box. We're going to try upgrading MySQL again (there have been some updates since I started this post). It is just such a weird problem...We'll see what happens.

Thank you all for your responses. I really appreciate it.

Sxooter

Have you tried the SQL spec

-- this is a comment

jenni

Yep...Same thing...Strange huh?

cheese

Is it possible to ghost the complete install across???

jenni

I'll run it by the guy who is going to do it. Thanks!

Sxooter

There are some switches you can set either at build time or when starting the daemon that turn certain features like this on and off. You might wanna check those.

jenni

Just wanted to give a final update. We upgraded to the next version of mysql and all is good. It must have been some funkiness with that version and how we had everything else configured.

Thanks for all of your help!