Skip site navigation (1) Skip section navigation (2)

Re: Proposal: new pg_dump options --copy-delimiter and

From: Greg Stark <gsstark(at)mit(dot)edu>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: new pg_dump options --copy-delimiter and
Date: 2006-01-27 18:12:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Joshua D. Drake" <jd(at)commandprompt(dot)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.

I think what he's getting at is for things like, say, a contrib package with a
README that includes an example. He wants to be able to say "just paste these
commands into psql".

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.


In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2006-01-27 18:22:22
Subject: Re: Proposal: new pg_dump options --copy-delimiter and
Previous:From: Joshua D. DrakeDate: 2006-01-27 17:44:40
Subject: Re: Adding a --quiet option to initdb

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group