On Tue, 2007-05-29 at 22:41 -0400, Tom Lane wrote:
> Jeff Davis <[EMAIL PROTECTED]> writes:
> > On Tue, 2007-05-29 at 18:10 +0100, Gregory Stark wrote:
> >> It has the same problem that SELECT triggers have. How many rows should you
> >> expect that subquery to insert, update, or delete if it's use
Jeff Davis <[EMAIL PROTECTED]> writes:
> On Tue, 2007-05-29 at 18:10 +0100, Gregory Stark wrote:
>> It has the same problem that SELECT triggers have. How many rows should you
>> expect that subquery to insert, update, or delete if it's used in a join
>> clause? Or in the where clause of another in
On Tue, 2007-05-29 at 18:10 +0100, Gregory Stark wrote:
> It has the same problem that SELECT triggers have. How many rows should you
> expect that subquery to insert, update, or delete if it's used in a join
> clause? Or in the where clause of another insert/update/delete statement?
>
We could h
"David Fetter" <[EMAIL PROTECTED]> writes:
> On Tue, May 29, 2007 at 09:41:38AM -0400, Tom Lane wrote:
>> "Jan Szumiec" <[EMAIL PROTECTED]> writes:
>> > UPDATE items SET (type, post_id) = (INSERT INTO efforts (effort) VALUES
>> > (667) RETURNING 'Item', id) WHERE id = 1937
>>
>> Sorry, RETURNING
On Tue, May 29, 2007 at 09:41:38AM -0400, Tom Lane wrote:
> "Jan Szumiec" <[EMAIL PROTECTED]> writes:
> > UPDATE items SET (type, post_id) = (INSERT INTO efforts (effort) VALUES
> > (667) RETURNING 'Item', id) WHERE id = 1937
>
> Sorry, RETURNING is only supported at the top level of a query.
Wha
"Jan Szumiec" <[EMAIL PROTECTED]> writes:
> UPDATE items SET (type, post_id) = (INSERT INTO efforts (effort) VALUES
> (667) RETURNING 'Item', id) WHERE id = 1937
Sorry, RETURNING is only supported at the top level of a query.
regards, tom lane
---(
The following bug has been logged online:
Bug reference: 3320
Logged by: Jan Szumiec
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Windows XP
Description:Error when using INSERT...RETURNING as a subquery
Details:
Having:
CREATE TABLE
