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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Gibellini Paolo | 2002-07-31 17:20:19 | ERROR: scanNameSpaceForRefname: unexpected node type 0 |
Previous Message | pgsql-bugs | 2002-07-31 13:27:38 | Bug #726: PHP/PG ERROR: parser: parse error at or near "," |