From: | Kyle Bateman <kyle(at)actarg(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | possible parser error |
Date: | 1999-06-25 21:07:53 |
Message-ID: | 3773EFA9.F354E501@actarg.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)actarg(dot)com (801)377-8033x101
----------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Doug Younger | 1999-06-26 04:31:17 | trigger to insert on update to non-existing row? |
Previous Message | Jim Rowan | 1999-06-25 20:48:25 | Re: [HACKERS] Re: trouble creating log table with rules |