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.
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2007-05-30 02:41:34|
|Subject: Re: BUG #3320: Error when using INSERT...RETURNING as a subquery |
|Previous:||From: Alceu Paz||Date: 2007-05-29 19:33:53|
|Subject: BUG #3321: No start service|