Skip site navigation (1) Skip section navigation (2)

Re: BUG #3320: Error when using INSERT...RETURNING as asubquery

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Szumiec <jan(dot)szumie(at)infiniteloop(dot)eu>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3320: Error when using INSERT...RETURNING as asubquery
Date: 2007-05-29 23:42:17
Message-ID: 1180482137.26915.93.camel@dogma.v10.wvs (view raw or flat)
Thread:
Lists: pgsql-bugs
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 handle it essentially like a volatile set-returning function.

It may be easy to shoot oneself in the foot, but that is true for many
uses of volatile functions.

If the argument is that we shouldn't make it any easier, that's a fair
point, but this is one possible definition.

Regards,
	Jeff Davis


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2007-05-30 02:41:34
Subject: Re: BUG #3320: Error when using INSERT...RETURNING as a subquery
Previous:From: Alceu PazDate: 2007-05-29 19:33:53
Subject: BUG #3321: No start service

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group