Re: Ragged CSV import

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Ragged CSV import
Date: 2009-09-10 11:08:55
Message-ID: 4AA8DE47.5070804@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
> On Wed, 2009-09-09 at 19:18 -0400, Robert Haas wrote:
>
>> I agree that ignoring extra columns is a bad idea, but I don't even
>> like the idea of ignoring missing columns. It doesn't seem like a
>> good idea to take a spreadsheet and feed it into COPY without doing
>> any validation anyway, and this is the kind of thing that is trivial
>> to clean up with a thin layer of Perl or your scripting language of
>> choice.
>>
>
> I would think that a spreadsheet application has some kind of control
> over its export format, too. Perhaps you can just tell it to export
> only the first N columns?
>
>

Not to my knowledge. In any case, this requires more user work and much
more user education, and in the situation I am dealing with neither is
likely.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-09-10 11:16:02 Re: Ragged CSV import
Previous Message Pavel Stehule 2009-09-10 10:46:41 Re: RfD: more powerful "any" types