Query error

[Anon]

I have a query that when passed to mysql_query() that will not execute (error) however when i input the same query into mysql at the Unix prompt it updates the database fine.

I am using PHP3.

Query = "INSERT INTO logbook SET Entry_Date='2001-04-13', Work_Summary='some work', Notes='hello.htm';"

Any ideas? thanks James.

[steved]

Have you tried it without the semi-colon at the end of your query?

[Anon]

The format you are using seems unnatural to me at first glance. I am not a super-experienced SQL guru, however heres what i observed:

I only use the \\'SET\\' command when i\\'m doing an \\'UPDATE\\' not an \\'INSERT INTO\\'. For \\'INSERT INTO\\' i use \\"INSERT INTO (column1,column2,column3,columnN) VALUES (\\'blah1\\',\\'blah2\\',\\'blah3\\',\\'blahN\\')\\";

Hope that helps.

[Anon]

I don't know how this would work from the command line, as it's not valid sql, to my knowledge. However, your answer is this: SET doesn't go with INSERT; it goes with UPDATE. for an INSERT command, use this syntax:

INSERT INTO table (field1, field2, ...) VALUES ('value1', 'value2', ...)

you don't need a semicolon at the end unless you have more statements after this one before you perform the query (and sometimes not even then.)

[[deleted]]

Did you try printing the mysql_error() after running the query, to see just why it's failing?

[[deleted]]

In MySQL, SET does go with INSERT.

MySQL doesn't like standards.

[Anon]

Touché.

[[deleted]]

Touche, cabriolet, et trottoir avec mon portefuille dans la pain du vain du boursain :-)

[kparker]

you don't need a semicolon at the end

Uhh, with mysql it's stronger than that: you musn't have a semicolon. (Or have they changed that in 3.23.x?)

[kparker]

But current versions do support the standard syntax, as shown by this just clipped from the online manual:

INSERT [LOW_PRIORITY | DELAYED] [IGNORE]
[INTO] tbl_name [(col_name,...)]
VALUES (expression,...),(...),...

So he really should modify it to use genuine SQL standard syntax.

[[deleted]]

Very good point, he should use the proper format.
Or SQL will play hell with his noodle if he ever switches to a "real" database.

But in this case, using an alternative format is not the cause of the error. :-)

[Anon]

Are you asking me to walk your horse to the bakery? Because I charge for that.

[[deleted]]

giggle