From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hans-J?rgen Sch?nig <postgres(at)cybertec(dot)at>, Paolo Magnoli <pmagnoli(at)systemevolution(dot)it>, pgsql-hackers(at)postgresql(dot)org, eg(at)cybertec(dot)at |
Subject: | Re: R: feature proposal ... |
Date: | 2005-09-22 19:25:53 |
Message-ID: | 20050922192553.GR7630@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 21, 2005 at 11:31:42AM -0400, Tom Lane wrote:
> =?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <postgres(at)cybertec(dot)at> writes:
> > Paolo Magnoli wrote:
> >> Can't you just use a view?
>
> > no because a new is not a heap ...
>
> I think Paolo's idea is much better than munging the syntax of COPY,
> though. Fixing COPY so that you *could* copy from a view would provide
> all the desired functionality without any syntactic warts.
While I'm all for COPY from views, I think I'd rather have the syntactic
warts than code warts. ISTM that
CREATE TEMP VIEW some_name AS SELECT * FROM table WHERE ...;
COPY some_name TO stdout;
is much uglier than
COPY SELECT * FROM table WHERE ... TO stdout;
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Hans-Juergen Schoenig | 2005-09-22 19:34:30 | Re: R: feature proposal ... |
Previous Message | Daniel Duvall | 2005-09-22 19:17:26 | Re: postgresql clustering |