Re: multiline CSV fields

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kris Jurka <books(at)ejurka(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: multiline CSV fields
Date: 2004-11-30 03:53:35
Message-ID: 200411300353.iAU3rZr17548@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> 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.

What pushed us was the large number of request for it.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2004-11-30 04:00:05 Re: Error handling in plperl and pltcl
Previous Message Robert Treat 2004-11-30 03:43:50 Re: bug fix request

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2004-11-30 04:34:13 Re: multiline CSV fields
Previous Message Tom Lane 2004-11-30 03:35:10 Re: multiline CSV fields