| From: | "Mark Woodward" <pgsql(at)mohawksoft(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: COPY (query) TO file |
| Date: | 2006-06-03 01:25:41 |
| Message-ID: | 18743.24.91.171.78.1149297941.squirrel@mail.mohawksoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>>> Allow COPY to output from views
>>> Another idea would be to allow actual SELECT statements in a COPY.
>>>
>>> Personally I strongly favor the second option as being more flexible
>>> than the first.
>>
>>
>> I second that - allowing arbitrary SELECT statements as a COPY source
>> seems much more powerful and flexible than just supporting COPY FROM
>> VIEW.
>
> Not to be a sour apple or anything but I don't see how any of this is
> needed in the backend since we can easily use Psql to do it, or pretty
> much any other tool.
There is an important difference between a capability in the backend vs
one synthesized in the frontend.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-06-03 01:44:53 | Re: COPY (query) TO file |
| Previous Message | Joshua D. Drake | 2006-06-03 00:48:03 | Re: COPY (query) TO file |