| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: multiline CSV fields |
| Date: | 2004-11-30 03:35:10 |
| Message-ID: | 5687.1101785710@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Kris Jurka <books(at)ejurka(dot)com> writes:
> Endlessly extending the COPY command doesn't seem like a winning
> proposition to me and I think if we aren't comfortable telling every user
> to write a script to pre/post-process the data we should instead provide a
> bulk loader/unloader that transforms things to our limited COPY
> functionality. There are all kinds of feature requests I've seen
> along these lines that would make COPY a million option mess if we try to
> support all of it directly.
I agree completely --- personally I'd not have put CSV into the backend
either.
IIRC we already have a TODO item for a separate bulk loader, but no
one's stepped up to the plate yet :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-11-30 03:43:10 | Re: Error handling in plperl and pltcl |
| Previous Message | Bruce Momjian | 2004-11-30 03:25:08 | Re: multiline CSV fields |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-11-30 03:53:35 | Re: multiline CSV fields |
| Previous Message | Bruce Momjian | 2004-11-30 03:25:08 | Re: multiline CSV fields |