| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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: | 2007-05-29 16:59:15 |
| Message-ID: | 20070529165915.GA1912@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, May 29, 2007 at 09:41:38AM -0400, Tom Lane wrote:
> "Jan Szumiec" <jan(dot)szumie(at)infiniteloop(dot)eu> 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.
What would be involved with making this possible? What we have at the
moment is a pretty clear POLA violation because unlike the rest of the
row-returning objects (tables, views, SRFs and VALUES() clauses), only
RETURNING can't be used in a subquery.
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-05-29 17:10:48 | Re: BUG #3320: Error when using INSERT...RETURNING as a subquery |
| Previous Message | Magnus Hagander | 2007-05-29 16:53:09 | Re: BUG #3318: PostgreSQL : server process (PID 3480) was terminated by signal 5 |