From: Kyle Bateman <kyle@actarg.com>
To: pgsql-sql@postgresql.org
Subject: possible parser error
Date: Fri, 25 Jun 1999 15:07:53 -0600
Message-ID: <3773EFA9.F354E501@actarg.com> (raw)
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.
--
----------------------------------------------------
Kyle Bateman President, Action Target Inc.
"Viva Yo!" kyle@actarg.com (801)377-8033x101
----------------------------------------------------
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: kyle@actarg.com
Subject: Re: possible parser error
In-Reply-To: <3773EFA9.F354E501@actarg.com>
References: <3773EFA9.F354E501@actarg.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox