From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Kyle Bateman <kyle(at)actarg(dot)com> |
Cc: | pgsql-ports(at)postgreSQL(dot)org |
Subject: | Re: [PORTS] Port Bug Report: parse error not detected on unterminated quote |
Date: | 1999-06-30 13:31:51 |
Message-ID: | 377A1C47.5E480EAB@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-ports pgsql-sql |
> 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 1999-06-30 13:48:59 | Re: [PORTS] Port Bug Report: Can't create indicies on type "timestamp" |
Previous Message | Unprivileged user | 1999-06-30 08:14:22 | Port Bug Report: when I configure --with-CXX make stops with this error fmgrtab.o:file not recognized: File format not recognized |
From | Date | Subject | |
---|---|---|---|
Next Message | Herouth Maoz | 1999-06-30 13:35:28 | Re: [SQL] String concat operator??? |
Previous Message | webmaster | 1999-06-30 13:16:31 | String concat operator??? |