Re: [PORTS] Port Bug Report: parse error not detected on unterminated quote - Mailing list pgsql-ports

From Thomas Lockhart
Subject Re: [PORTS] Port Bug Report: parse error not detected on unterminated quote
Date
Msg-id 377A1C47.5E480EAB@alumni.caltech.edu
Whole thread Raw
In response to Port Bug Report: parse error not detected on unterminated quote  (Unprivileged user <nobody>)
Responses Re: [PORTS] Port Bug Report: parse error not detected on unterminated quote
List pgsql-ports
> Problem Description:
> --------------------
> If a single quote is left unmatched in the query, the parser
> seems to throw away the rest of the line without detecting
> an error.
> Test Case:
> ----------
> Enter a select like this:
> select * from mytable where id = 1234;
> You should get only one record.
>
> Now put in an errant single quote:
> select * from mytable' where id = 1234;
> Now you get the whole table.  This should really be a
> syntax error of some kind.

And seems to be:

postgres=> select * from mytable' where id = 1234;
postgres'> '
postgres-> ;
ERROR:  parser: parse error at or near "'"
postgres=>

This is on a RH5.2 system with with the cvs distribution of Postgres
(rather than v6.5 exactly). But the parsing behavior should be the
same. I'm not sure what could be different in our installations...

                     - Thomas

--
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California

pgsql-ports by date:

Previous
From: Unprivileged user
Date:
Subject: Port Bug Report: when I configure --with-CXX make stops with this error fmgrtab.o:file not recognized: File format not recognized
Next
From: Thomas Lockhart
Date:
Subject: Re: [PORTS] Port Bug Report: Can't create indicies on type "timestamp"