Re: Ragged CSV import - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Ragged CSV import
Date
Msg-id 4AA7CE24020000250002ABEE@gw.wicourts.gov
Whole thread Raw
In response to Re: Ragged CSV import  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Ragged CSV import
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> wrote:
> Would this just work on columns on the end, or would it work on the
> basis of parsing the CSV header and matching columns?
> 
> While the former functionality would be relatively simple, I think
the
> latter is what people really want.
It's been a while since I've had a need for something like this, but
of
the copy features not currently available in PostgreSQL, the two most
useful are to read in only some of the defined columns, and to output
to
a separate disk file any rows which failed to match the expected
format.
The latter would not cause the copy to fail unless the count of such
rows exceeded a user-specified threshold.
-Kevin


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Ragged CSV import
Next
From: Hannu Krosing
Date:
Subject: Re: RfD: more powerful "any" types