From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | ishii(at)postgresql(dot)org, andrew(at)dunslane(dot)net, pgsql(at)markdilger(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: utf8 COPY DELIMITER? |
Date: | 2007-04-18 01:24:42 |
Message-ID: | 20070418.102442.00486914.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
> > The message in question should be something like:
> > "COPY delimiter must be a single ASCII character"
>
> If we phrase it like that we should enforce it like that --- ie, reject
> high-bit-set characters.
>
> But I'm a bit hesitant to do so, because it actually does work fine to
> use a high-bit-set character as a delimiter as long as client and server
> encodings are the same LATINx set. We'd be taking away functionality
> for European users for no very good reason.
>
> Is it worth going to the trouble of distinguish same-encoding and
> different-encoding cases and applying a looser check for the former
> case?
I think yes. Seems a good idea.
Even better, however, is fixing the CVS escaping and quoting I
think. Clearly it's a bug.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-04-18 01:25:34 | Re: Autovacuum vs statement_timeout |
Previous Message | Joshua D. Drake | 2007-04-18 01:22:28 | Re: Autovacuum vs statement_timeout |