| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Ragged CSV import |
| Date: | 2009-09-10 13:56:24 |
| Message-ID: | 22797.1252590984@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dimitri Fontaine <dfontaine(at)hi-media(dot)com> writes:
> Last time we opened this can of worms here's what it lead us to:
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg00222.php
Right, that's the discussion I was remembering.
> As already said by Andrew on IRC, though, this goes nowhere to help him
> address his direct concern, COPY would still choke on input lines that
> are containing too few or too many columns...
An easy fix for that is to allow this form of COPY to return text[]
instead of a fixed number of text columns.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-09-10 13:56:29 | Re: Ragged CSV import |
| Previous Message | Kristian Larsson | 2009-09-10 13:42:52 | Re: Adding integers ( > 8 bytes) to an inet |