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

Re: multiline CSV fields

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: multiline CSV fields
Date: 2004-11-29 08:04:38
Message-ID: 10081.1101715478@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Chris GreenDate: 2004-11-29 08:50:51
Subject: Re: Adding Reply-To: <listname> to Lists configuration ...
Previous:From: Christopher Kings-LynneDate: 2004-11-29 07:58:21
Subject: Re: bug fix request

pgsql-patches by date

Next:From: Troels ArvinDate: 2004-11-29 10:15:13
Subject: Re: SQL conformance related patch
Previous:From: Andrew DunstanDate: 2004-11-29 07:34:26
Subject: Re: multiline CSV fields

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