From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: COPY IN as SELECT target |
Date: | 2009-12-18 13:15:02 |
Message-ID: | 4B2B8056.8020405@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule wrote:
> 2009/12/17 Andrew Dunstan <andrew(at)dunslane(dot)net>:
>
>> 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 ...
>>
>>
>> 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;
>>
>> Thoughts?
>>
>
> In this case copy doesn't return array - so RETURNING ARRAY is little
> bit strange.
>
> what
>
> SELECT .. FROM (COPY VALUES [(colums)] FROM ....)
>
>
You are misunderstanding what I want to provide, which is that it *does*
return an array of text for each line. That was what the previous
discussion arrived at, and is illustrated in the example I showed above.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-12-18 14:00:47 | Re: Largeobject Access Controls (r2460) |
Previous Message | Peter Eisentraut | 2009-12-18 12:57:59 | Re: Fast or immediate shutdown |