Re: multiline CSV fields - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: multiline CSV fields
Date
Msg-id 200411291300.iATD0Ke27741@candle.pha.pa.us
Whole thread Raw
In response to Re: multiline CSV fields  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: multiline CSV fields  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom Lane wrote:
> >> Which we do not have, because pg_dump doesn't use CSV.  I do not think
> >> this is a must-fix, especially not if the proposed fix introduces
> >> inconsistencies elsewhere.
> 
> > Sure, pg_dump doesn't use it but COPY should be able to load anything it
> > output.
> 
> I'd buy into that proposition if CSV showed any evidence of being a
> sanely defined format, but it shows every indication of being neither
> well-defined, nor self-consistent, nor even particularly portable.
> I suggest adjusting your expectations.  All I expect from that code is
> being able to load the majority of data from the more popular Microsloth
> applications.  Trying to achieve 100% consistency for corner cases is
> just going to interfere with the real use-case for the feature, which is
> coping with output from applications that aren't very consistent in the
> first place.

OK, then should we disallow dumping out data in CVS format that we can't
load?  Seems like the least we should do for 8.0.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: jseymour@linxnet.com (Jim Seymour)
Date:
Subject: Re: [GENERAL] Adding Reply-To: to Lists configuration ...
Next
From: Bruce Momjian
Date:
Subject: Re: Documentation on PITR still scarce