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

From Andrew Dunstan
Subject Re: Proposal: new pg_dump options --copy-delimiter and
Date
Msg-id 1138388709.3074.35.camel@swithin
Whole thread Raw
In response to Re: Proposal: new pg_dump options --copy-delimiter and  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposal: new pg_dump options --copy-delimiter and  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 2006-01-27 at 13:43 -0500, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
> > I could not disagree more. The invisibility of tabs makes their use as a
> > delimiter wholly evil. I have lost count of the number of corrupted
> > makefiles etc. I have seen because a tab got converted to a space and it
> > was impossible to tell.
> 
> > More tears have been shed over tabs used than tabs unused. (Apologies to
> > St Theresa).
> 
> That line of argument leads to the suggestion that pg_dump should just
> use something else (I'd vote for "|"), all the time, in order to produce
> more robust dump files.  I still don't see the argument for exposing
> a switch though.
> 


If we regard them as suitable for human editing for normal use, yes.

cheers

andrew



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposal: new pg_dump options --copy-delimiter and
Next
From: Tom Lane
Date:
Subject: Re: Proposal: new pg_dump options --copy-delimiter and