From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Eric Ridge <eebbrr(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |
Date: | 2011-11-01 18:04:23 |
Message-ID: | CAFj8pRDwXqOfDq-WA=-45=TM+V=xhtrLrnGhD8EAxn7fT5nRKw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2011/11/1 Eric Ridge <eebbrr(at)gmail(dot)com>:
> 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.
I understand it, it is really bad idea use a star in export queries
Pavel
>
> eric
>
> ps, it seems my messages aren't hitting the list? weird.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2011-11-01 18:05:43 | Re: Compiler branch prediction hints (was: So, is COUNT(*) fast now?) |
Previous Message | Eric Ridge | 2011-11-01 18:01:36 | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |