Since I replied only to Edwin. ----- Original Message ----- From: "Bob Eldred" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 18, 2004 10:40 PM Subject: Re: [PHP] Parse Error
> Yes. Of course not. That wasn't the point. The point was that the > parse error isn't caused by the lack of single quotes. > > Were everything else right in the script, that query would be just fine. > > ----- Original Message ----- > From: "- Edwin -" <[EMAIL PROTECTED]> > To: "Bob Eldred" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Wednesday, February 18, 2004 10:04 PM > Subject: Re: [PHP] Parse Error > > > > On Wed, 18 Feb 2004 21:35:15 -0800 > > "Bob Eldred" <[EMAIL PROTECTED]> wrote: > > > > > > The error is: > > > > Parse error: parse error, unexpected T_VARIABLE in > > > > /www/htdocs/rolfvand/thinkquest/browsercheck.php on line 46 > > > > [/snip] > > > > > > > > All of your values are not enclosed with single quotes - the > > > > first > > > four > > > > are, last four aren't > > > > > > That's almost definitely not the issue. Worst case scenario > > > with the non-existent quotes is that MySQL will put bad > > > information into the database if it's expecting numbers there > > > and gets a string, or the query will fail if it's a string with > > > whitespace. It ought to parse just fine. > > > > ?? > > > > Your query wouldn't even be executed if you have a "parse error" > > on your script. (So, it's not even possible for MySQL to "put bad > > information into the database"...) Single quotes, double quotes, > > semi-colon ought to be checked if one has "Parse error: parse > > error, unexpected T_VARIABLE in blah blah blah"... > > > > ...[snip]... > > > > -- > > > > - E - > > > > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
