[SOLVED] Something wrong with my syntax!?

[bobleny]

Something wrong with my syntax!?

$sql = "UPDATE `options` SET `set` = '1' WHERE `name` = `signup`";

 

It keeps giving me this error:

Unknown column 'signup' in 'where clause'

 

I don't know what is wrong.

[AndyB]

$sql = "UPDATE `options` SET `set` = '1' WHERE `name` = 'signup'";

 

The above will work.  By the way, using reserved words as field names and being forced to use backticks all the time is not a very good practice.

[bobleny]

The above will work.  By the way, using reserved words as field names and being forced to use backticks all the time is not a very good practice.

 

Hmm... Could you explain?

I'm not sure what you mean by "reserved words".

I thought you where supposed to use "backticks"?

[bubblegum.anarchy]

MySQL is interpretting the backtick quoted signup string as a table name rather than a string... wrap insert strings with single quotes.

[AndyB]

Using MySQL reserved words for table names or field names is a very bad practice.  Using backticks is a sloppy work-around for scripts where reserved words have been used for table names or field names.  Avoid the problem and the backticks by checking the list of MySQL reserved words ... in the manual.

 

http://dev.mysql.com/doc/refman/5.0/en/reserved-words.html

 

Don't confuse those awful `backticks` with perfectly good 'quotes'.

[bobleny]

Ok, thanks. I'll keep that in mind for next time, but I'll still use the "backticks"

[AndyB]

... but I'll still use the "backticks"

Why?

[bobleny]

... but I'll still use the "backticks"

Why?

 

Do you really think they are that bad? I thought they added a big of organization to MySQL strings.

 

If you really think they are a bad thing then I'll consider not using them?

[fenway]

They are bad... don't use them.