Re: possible parser error

(I'm cleaning out old email tonight...)

A good long while ago, you wrote:
> I'm using v6.5. I found out accidentally that the query:

> update table set field = value' where key = keyvalue; --notice
> the accidental tick

> silently ignores everything after the tick and does not generate any
> kind of syntax error. This quietly clobbered a table by updating the
> field in every record in the table. (The where clause was ignored.)

> The tick shouldn't have been there, it was just a typing error. But
> unless I'm missing something, it seems like it would be good to
> generate an error like "Unmatched quotes" or some such thing.

FWIW, this is fixed in 7.0. I do not believe it's possible to make
this sort of mistake in psql (because psql won't send an incomplete
quoted string to the backend), but it's surely possible in other
interfaces or when using libpq directly. 7.0 gives:

ERROR: Unterminated quoted string

regards, tom lane