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

From David Fetter
Subject Re: Proposal: new pg_dump options --copy-delimiter and
Date
Msg-id 20060203011006.GA10513@fetter.org
Whole thread Raw
In response to Re: Proposal: new pg_dump options --copy-delimiter and  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
On Fri, Jan 27, 2006 at 01:12:35PM -0500, Greg Stark wrote:
> 
> "Joshua D. Drake" <jd@commandprompt.com> writes:
> 
> > 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.
> 
> The problems are a) there's no guarantee the data is safe to put through your
> hypothetical tab-destroying copy/paste anyways. There could be tabs or other
> unsafe characters in the data. b) We have no way of knowing which characters
> are or aren't safe in your hypothetical copy/paste system. Why is tab unsafe
> in the first place?
> 
> Personally I find anything that would encourage people to use anything other
> than tabs evil anyways. All those people who think | is somehow a reasonable
> choice or want to use commas and then get all confused trying to escape them
> and invent ever more confused syntaxes for escaping the escape characters.
> Just use tab separated data like man was meant to.

I'd say that the multiplicity of strong opinions on The Right
Delimiter is a pretty strong argument for having a switch to control
it.

Cheers,
D
-- 
David Fetter david@fetter.org http://fetter.org/
phone: +1 415 235 3778

Remember to vote!


pgsql-hackers by date:

Previous
From: Chris Campbell
Date:
Subject: Passing arguments to views
Next
From: Bruce Momjian
Date:
Subject: Re: Backslashes in string literals