Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #3320: Error when using INSERT...RETURNING as a subquery
- 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 a subquery
- Date: Tue, 29 May 2007 16:42:17 -0700
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
- Follow-Ups:
- References:
- BUG #3320: Error when using INSERT...RETURNING as a subquery
- From: Jan Szumiec
- Re: BUG #3320: Error when using INSERT...RETURNING as a subquery
- From: Tom Lane
- Re: BUG #3320: Error when using INSERT...RETURNING as a subquery
- From: David Fetter
- Re: BUG #3320: Error when using INSERT...RETURNING as a subquery
- From: Gregory Stark
- BUG #3320: Error when using INSERT...RETURNING as a subquery
- Prev by Date: BUG #3321: No start service
- Next by Date: Re: BUG #3320: Error when using INSERT...RETURNING as a subquery
- Previous by thread: Re: BUG #3320: Error when using INSERT...RETURNING as a subquery
- Next by thread: Re: BUG #3320: Error when using INSERT...RETURNING as a subquery
- Indexes: