Re: [BUGS] BUG #6572: The example of SPI_execute is bogus - Mailing list pgsql-hackers

From Boszormenyi Zoltan
Subject Re: [BUGS] BUG #6572: The example of SPI_execute is bogus
Date
Msg-id 4F8A917E.4020305@cybertec.at
Whole thread Raw
In response to Re: [BUGS] BUG #6572: The example of SPI_execute is bogus  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [BUGS] BUG #6572: The example of SPI_execute is bogus
List pgsql-hackers
2012-04-14 18:15 keltezéssel, Peter Eisentraut írta:
> On lör, 2012-04-14 at 08:23 -0400, Robert Haas wrote:
>> On Sat, Apr 14, 2012 at 3:27 AM, Pavel Stehule<pavel.stehule@gmail.com>  wrote:
>>>> It has a lot of sense.  Without it, it's very difficult to do logical
>>>> replication on a table with no primary key.
>>>>
>>>> (Whether or not people should create such tables in the first place
>>>> is, of course, beside the point.)
>>> I am not against to functionality - I am against just to syntax DELETE
>>> FROM tab LIMIT x
>>>
>>> because is it ambiguous what means: DELETE FROM tab RETURNING * LIMIT x
>> What's ambiguous about that?
> I suppose one could wonder whether the LIMIT applies to the deleting or
> just the returning.

Ambigous only in this order. LIMIT x RETURNING * wouldn't be.

--
----------------------------------
Zoltán Böszörményi
Cybertec Schönig&  Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de     http://www.postgresql.at/



pgsql-hackers by date:

Previous
From: Brendan Jurd
Date:
Subject: Re: Clobbered parameter names via DECLARE in PL/PgSQL
Next
From: Pavel Stehule
Date:
Subject: Re: [BUGS] BUG #6572: The example of SPI_execute is bogus