| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: COPY for CSV documentation |
| Date: | 2004-04-12 02:39:13 |
| Message-ID: | 28346.1081737553@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> That's what I was wondering. Is triggering CSV for multi-character
> delimiters a little too clever? This reminds me of the use of LIMIT X,Y
> with no indication which is limit and which is offset.
I agree, this seems risky and not at all readable to someone who doesn't
remember exactly how the parameter is defined.
>> COPY a FROM stdin WITH DELIMITER "," QUOTE '"' EQUOTE '"';
> EQUOTE for embedded quote.
ESCAPE would be better no? It's already a keyword ...
BTW, don't forget that the syntax options have to be provided in psql's
\copy as well. Did the patch cover that?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-04-12 03:11:17 | Re: COPY for CSV documentation |
| Previous Message | Bruce Momjian | 2004-04-12 02:25:53 | Re: Russian FAQ update |