Re: why generated columsn cannot be used in COPY TO? - Mailing list pgsql-general

From Adrian Klaver
Subject Re: why generated columsn cannot be used in COPY TO?
Date
Msg-id 4edb5259-10e6-4103-9d4b-9d63992a6a91@aklaver.com
Whole thread Raw
In response to Re: why generated columsn cannot be used in COPY TO?  (Ron <ronljohnsonjr@gmail.com>)
Responses Re: why generated columsn cannot be used in COPY TO?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On 10/6/23 08:45, Ron wrote:
> On 10/6/23 09:04, Andreas Kretschmer wrote:
>>

>>> Not sure how convincing that reasoning is, but it was at least
>>> thought about.  I do agree with it as far as the default column
>>> list goes, but maybe we could allow explicit selection of these
>>> columns in COPY TO.
>>
>> sounds okay
> 
> Nah.  "The programmer -- and DBA -- on the Clapham omnibus" quite 
> reasonably expects that COPY table_name TO (output)" copies all the 
> columns listed in "\d table_name".
> 

Yeah, I would agree.

> -- 
> Born in Arizona, moved to Babylonia.

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: why generated columsn cannot be used in COPY TO?
Next
From: "David G. Johnston"
Date:
Subject: Re: why generated columsn cannot be used in COPY TO?