| From: | Eric Ridge <eebbrr(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |
| Date: | 2011-11-01 18:01:36 |
| Message-ID: | CANcm6waaPok=wooh4L+d3KxkWJBj1JK-Bac5K72k=hpL-AgXAg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 1, 2011 at 1:33 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> COPY (SELECT * EXCLUDING (a, b, c) FROM <big query>) TO 'somefile.csv' WITH CSV;
>>
> sorry, I don't accept it. I am able to understand your request for
> adhoc queries. But not for COPY.
I apologize if that example was confusing. I wasn't also suggesting
expanding COPY's syntax. I was merely pointing out that if
"EXCLUDING(…)" were implemented, you'd be able to use it within the
query given to the COPY command.
eric
ps, it seems my messages aren't hitting the list? weird.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2011-11-01 18:04:23 | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |
| Previous Message | Robert Haas | 2011-11-01 17:57:59 | Re: pg_upgrade if 'postgres' database is dropped |