From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: COPY for CSV documentation |
Date: | 2004-04-11 01:06:02 |
Message-ID: | 200404110106.i3B162b24677@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
>
> >I have reviewed this patch. Basically, CSV is enabled by specifying
> >more than one delimiter character to COPY, e.g. DELIMITER ',"' or
> >DELIMITER ',""'. Is this API good for folks?
> >
>
> (if not I'll be displeased, as it is what was the general consensus
> about a month ago)
OK
> >Prior to 7.2, a multi-character delimiter could be specified, but only
> >the first character was used. 7.2 release notes state:
> >
> > * COPY DELIMITERS string must be exactly one character (Tom)
> >
> >I am a little worried about multibyte too, as you mentioned.
> >
>
> I am not sure that CSVs even make sense in a multibyte world. If not, it
> would make sense to disable it in such a case.
>
> (Is that your only worry?)
Yes, my worry is that someone will use a multibyte character that the
system sees as several bytes and enters CSV mode.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-04-11 01:45:05 | Re: New socket code for win32 |
Previous Message | Bruce Momjian | 2004-04-11 01:00:28 | Re: [HACKERS] Function to kill backend |