From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: multiline CSV fields |
Date: | 2004-11-30 01:36:42 |
Message-ID: | Pine.BSO.4.56.0411292031090.15008@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mon, 29 Nov 2004, Andrew Dunstan wrote:
> Longer term I'd like to be able to have a command parameter that
> specifies certain fields as multiline and for those relax the line end
> matching restriction (and for others forbid multiline altogether). That
> would be a TODO for 8.1 though, along with optional special handling for
> first line column headings.
>
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.
- skipping header rows
- skipping certain data file columns
- specifying date formats
- ignoring duplicates
- outputting an arbitrary SELECT statement
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-11-30 02:43:39 | Re: Opinions on Usenet ... |
Previous Message | Mark Wong | 2004-11-30 00:01:29 | 8.0beta5 results w/ dbt2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-11-30 03:25:08 | Re: multiline CSV fields |
Previous Message | Roland Volkmann | 2004-11-30 01:05:31 | Re: Charset WIN1252 |