| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY IN as SELECT target |
| Date: | 2009-12-17 17:23:30 |
| Message-ID: | 4B2A6912.1080509@enterprisedb.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
> Recently there was discussion about allowing a COPY statement to be a
> SELECT target, returning a text array, although the syntax wasn't really
> nailed down that I recall. I was thinking that we might have
>
> COPY RETURNING ARRAY FROM ...
>
> instead of
>
> COPY tablename opt_column_list FROM ...
It's not really returning an array, is it? It's returning a bag of rows
like a (sub)query.
> the we possibly could do things like:
>
> SELECT t[5] as a, 3*(t[3]::numeric) as b FROM (COPY RETURNING ARRAY
> FROM STDIN CSV) as t;
How about just COPY FROM? As in
SELECT t[5] as a, 3*(t[3]::numeric) as b FROM (COPY FROM STDIN CSV) as t
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-17 17:28:50 | Re: COPY IN as SELECT target |
| Previous Message | Kevin Grittner | 2009-12-17 17:17:20 | Re: determine snapshot after obtaining locks for first statement |