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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Green | 2004-11-29 08:50:51 | Re: Adding Reply-To: <listname> to Lists configuration ... |
Previous Message | Christopher Kings-Lynne | 2004-11-29 07:58:21 | Re: bug fix request |
From | Date | Subject | |
---|---|---|---|
Next Message | Troels Arvin | 2004-11-29 10:15:13 | Re: SQL conformance related patch |
Previous Message | Andrew Dunstan | 2004-11-29 07:34:26 | Re: multiline CSV fields |