Re: Implementation of LIMIT on DELETE and UPDATE statements (rel to 7.2.1)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: srb(at)cuci(dot)nl (Stephen R(dot) van den Berg)
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Implementation of LIMIT on DELETE and UPDATE statements (rel to 7.2.1)
Date: 2002-09-23 14:37:00
Message-ID: 21423.1032791820@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

srb(at)cuci(dot)nl (Stephen R. van den Berg) writes:
> Anyway, since ctid's solve my problem, I'm not particularly keen on
> getting the LIMIT support on UPDATE/DELETE anymore.
> I still think that the ctid solution is ugly and non-portable.

Well, they're both ugly and nonportable, IMHO.

To me the deciding argument is that the LIMIT approach is also
dangerous, because it encourages people to use incompletely-specified
queries to modify their data. See other messages in this thread for
examples.

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2002-09-23 15:13:39 Default privileges for 7.3
Previous Message Tom Lane 2002-09-23 14:01:06 Re: DROP COLUMN misbehaviour with multiple inheritance