Re: Proposal: new pg_dump options --copy-delimiter and - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Proposal: new pg_dump options --copy-delimiter and
Date
Msg-id 43DA39D2.9010205@commandprompt.com
Whole thread Raw
In response to Re: Proposal: new pg_dump options --copy-delimiter and --copy-null  (David Fetter <david@fetter.org>)
Responses Re: Proposal: new pg_dump options --copy-delimiter and
List pgsql-hackers
> Those who don't use it will never see it.
>   
It does however add more maintenance to the code.


>> Furthermore, it's quite unclear why you'd use pg_dump at all to
>> generate a data file that you intend to feed to some other program.
>>     
>
> In my case, it's about being copy/paste friendly.
>   
David I don't get this... what are you copying from/to that would
wouldn't just script? If you throw into a script you can change
the delimiter on the fly using translation.

> Actually, it's not.  I'm attaching my preliminary patch, as I see I
> haven't explained it well enough.
>   
Perhaps a test case that shows the productivity of it? I am not
arguing whether or not this is a useful feature but I don't
see the purpose.

Sincerely,

Joshua D. Drake


> Cheers,
> D
>   

-- 
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PLphp, PLperl - http://www.commandprompt.com/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Adding a --quiet option to initdb
Next
From: Thomas Hallgren
Date:
Subject: Re: Adding a --quiet option to initdb