Re: [PORTS] Port Bug Report: parse error not detected on unterminated quote

From: Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il>
To: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, 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 14:19:28
Message-ID: l03130306b39fd51af2c4@[147.233.159.109]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-ports pgsql-sql

At 16:31 +0300 on 30/06/1999, Thomas Lockhart wrote:

> 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...

In psql, it will probably never be a problem, because it demands that you
close the quotation mark (that "postgres'>" prompt). It doesn't send
anything to the backend until you have closed the quotation and type \g or
';'.

But what happens if the above query is sent through one of the other
interfaces, like pqlib?

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma

In response to

Responses

Browse pgsql-ports by date

  From Date Subject
Next Message Kyle Bateman 1999-06-30 14:36:55 Re: [PORTS] Port Bug Report: parse error not detected onunterminated quote
Previous Message Thomas Lockhart 1999-06-30 13:48:59 Re: [PORTS] Port Bug Report: Can't create indicies on type "timestamp"

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 1999-06-30 14:28:51 Re: [SQL] More fun with random selects
Previous Message Tom Lane 1999-06-30 14:18:06 Re: [SQL] String concat operator???