agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: Andreas Joseph Krogh <andreas@visena.com>
To: pgsql-sql@postgresql.org
Subject: Re: Unable to use INSERT ... RETURNING with column from other table
Date: Wed, 25 Oct 2017 23:34:05 +0200 (CEST)
Message-ID: <VisenaEmail.95.f144c8bcce132f5.15f557494e3@tc7-visena> (raw)
In-Reply-To: <15480.1508900684@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
På onsdag 25. oktober 2017 kl. 05:04:44, skrev Tom Lane <tgl@sss.pgh.pa.us
<mailto:tgl@sss.pgh.pa.us>>:
Peter Geoghegan <pg@bowt.ie> writes:
> As David says, you could use multiple CTEs for this.
Yeah. The SELECT portion of the query, so far as the outer INSERT
is concerned, is just a black box that yields some column values to
be inserted. We could wish that the INSERT's RETURNING clause
could examine additional column values that are available inside that
subquery, but I'm afraid that there are insurmountable semantic problems.
In particular, DISTINCT seems to break that entirely --- consider
insert into foo(id, name)
select distinct 3, f.name
from foo f
where ...
returning id, f.id;
We can't just add "f.id" to the set of columns returned by the SELECT
part without changing the semantics of the DISTINCT. Or if we ignore
that (acting like it was DISTINCT ON (3, f.name)) then we get an
underdetermined value of f.id, which doesn't seem appetizing either.
regards, tom lane
Thanks for the detailed explaination.
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas@visena.com <mailto:andreas@visena.com>
www.visena.com <https://www.visena.com;
<https://www.visena.com;
view thread (9+ messages)
Message-ID: <VisenaEmail.95.f144c8bcce132f5.15f557494e3@tc7-visena>
Permalink: ../VisenaEmail.95.f144c8bcce132f5.15f557494e3@tc7-visena/
Also on: postgresql.org/message-id/VisenaEmail.95.f144c8bcce132f5.15f557494e3@tc7-visena
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: andreas@visena.com
Subject: Re: Unable to use INSERT ... RETURNING with column from other table
In-Reply-To: <VisenaEmail.95.f144c8bcce132f5.15f557494e3@tc7-visena>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox