From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: DELETE syntax on JOINS |
Date: | 2009-08-25 13:57:38 |
Message-ID: | 4A93EDD2.9050201@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>
>> On Mon, Aug 24, 2009 at 9:31 PM, Josh Berkus<josh(at)agliodbs(dot)com> wrote:
>>
>>> What I don't get is why this is such a usability issue. Subqueries in
>>> DELETE FROM work perfectly well, and provide more flexibility than most
>>> users know what to do with.
>>>
>
>
>> It's both a usability issue and a performance issue.
>>
>
> On the usability front: if we were to take the position Josh advocates,
> we should never have added FROM/USING to UPDATE/DELETE at all
FWIW, I use update ... from a lot - it make many update queries easier
and less error prone to write - but I rarely find I need delete ... using.
> ... but
> since we did, I think we should try to make it as flexible as the
> corresponding feature in other DBMSes.
>
>
>
+1
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-08-25 14:08:10 | Re: DELETE syntax on JOINS |
Previous Message | Tom Lane | 2009-08-25 13:50:17 | Re: DELETE syntax on JOINS |