Re: COPY for CSV documentation - Mailing list pgsql-patches

From Tom Lane
Subject Re: COPY for CSV documentation
Date
Msg-id 28915.1081741225@sss.pgh.pa.us
Whole thread Raw
In response to Re: COPY for CSV documentation  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> In other words, the string after CSV is optional.  However, looking at
> the COPY syntax, there isn't any case where we have an optional string
> after a keyword.  Is that OK?

Seems better to avoid it.

> However, this still has CSV using a two-character string with special
> meaning for the first and second characters.

One point that I don't think was made before is that if we do any such
thing, we'll be forever foreclosing any chance of allowing
multi-character delimiters.  ISTM that would not be forward-looking.

            regards, tom lane

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Russian FAQ update
Next
From: "Andrew Dunstan"
Date:
Subject: Re: COPY for CSV documentation