Skip site navigation (1) Skip section navigation (2)

Re: Bug #726: PHP/PG ERROR: parser: parse error at or near

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: <predd-laflamme(at)strata-g(dot)com>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug #726: PHP/PG ERROR: parser: parse error at or near
Date: 2002-07-31 16:00:23
Message-ID: 20020731085926.J17229-100000@megazone23.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Wed, 31 Jul 2002 pgsql-bugs(at)postgresql(dot)org wrote:

> Paul Redd-LaFlamme (predd-laflamme(at)strata-g(dot)com) reports a bug with a severity of 1
> The lower the number the more severe it is.
>
> Short Description
> PHP/PG ERROR: parser: parse error at or near ","
>
> Long Description
> The SQL statement
> INSERT INTO users (user_name, comp_id, password) VALUES ('Yuk',8,'Yuk');
>
> works fine when typed directly into the postgres shell, but yields the error
>
> ERROR: parser: parse error at or near ","
>
> when, and only when the '8' is inserted into the string in PHP by any means.
>

> In other words, the SQL statement provided works fine when hardcoded,
> but fails every single time (making my application useless) when the
> integer insert value is inserted into the PHP statement by any means.

Try turning on query logging to see what sql statement the backend thinks
it's getting.


In response to

Responses

pgsql-bugs by date

Next:From: Gibellini PaoloDate: 2002-07-31 17:20:19
Subject: ERROR: scanNameSpaceForRefname: unexpected node type 0
Previous:From: pgsql-bugsDate: 2002-07-31 13:27:38
Subject: Bug #726: PHP/PG ERROR: parser: parse error at or near ","

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group