Re: BUG #4220: delete statement deleted too many rows - Mailing list pgsql-bugs

From Lon Varscsak
Subject Re: BUG #4220: delete statement deleted too many rows
Date
Msg-id 84cfc0470806041358g4a692c5ata13348d29b9ef58d@mail.gmail.com
Whole thread Raw
In response to Re: BUG #4220: delete statement deleted too many rows  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #4220: delete statement deleted too many rows
List pgsql-bugs
Wow, I want it to violate the spec so I can get my rows back! :)
I understand the problem and why it did what it did now though.

Thanks for your help,

Lon

On Wed, Jun 4, 2008 at 1:08 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> hubert depesz lubaczewski <depesz@depesz.com> writes:
> > On Wed, Jun 04, 2008 at 06:46:42PM +0000, Lon Varscsak wrote:
> >> delete from customer_transactions_detail where transaction_id in (select
> >> transaction_id from test);
> >> The transaction_id column does NOT exist in the temporary table named
> >> 'test').  I would think this would just result in an error, instead it
> >> delete all rows in the customer_transactions_detail table.
>
> > i wrote about it in more details in here:
> > http://www.depesz.com/index.php/2007/09/06/postgresql-gotchas/
>
> This isn't a "postgres gotcha", it's a "SQL standard gotcha".  Any DBMS
> that fails to execute the query exactly that way is violating the spec.
>
>                        regards, tom lane
>

pgsql-bugs by date:

Previous
From: Nathan Reed
Date:
Subject: Re: BUG #4219: fseeko test failure in configure script
Next
From: Tom Lane
Date:
Subject: Re: BUG #4219: fseeko test failure in configure script