Bruce Momjian [EMAIL PROTECTED] 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
Andrew Dunstan wrote:
I am thinking just:
COPY a FROM stdin WITH CSV ',';
or
COPY a FROM stdin WITH DELIMITER , QUOTE '' EQUOTE '';
EQUOTE for embedded quote. These are used in very limited situations
and don't have to be reserved words or anything.
I can help with these
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] 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
- Original Message -
From: Bruce Momjian [EMAIL PROTECTED]
Sent: April 11, 2004 10:25 PM
Serguei Mokhov wrote:
Hello,
This update fixes a few small typos in names,
pronouns and formatting in the Russian FAQ.
To Victor:
Why do you use the translit encoding for FAQ
Bruce Momjian [EMAIL PROTECTED] 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
