Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-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                        |
  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

pgsql-hackers by date

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

pgsql-patches by date

Next:From: Andrew DunstanDate: 2004-11-30 04:34:13
Subject: Re: multiline CSV fields
Previous:From: Tom LaneDate: 2004-11-30 03:35:10
Subject: Re: multiline CSV fields

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group