| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Mark Dilger <pgsql(at)markdilger(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: utf8 COPY DELIMITER? |
| Date: | 2007-04-17 17:37:58 |
| Message-ID: | 462505F6.3040405@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mark Dilger wrote:
> Andrew Dunstan wrote:
>> Mark Dilger wrote:
>>> The \COPY command rejects multibyte delimiters. Is this intentional
>>> behavior?
>>
>> It is certainly a known limitation, and I suspect removing it could
>> add non-trivial overhead to the input processing.
>>
>> What is the use case for using such a delimiter?
>
> I'm working on fixing bugs relating to multibyte character encodings.
> I wasn't sure whether this was a bug or not. I don't think we should
> use the phrasing "COPY delimiter must be a single character" when, in
> utf8 land, I did in fact use a single character. We might say "a
> single byte", or we might extend the functionality to handle multibyte
> characters.
>
Doing the latter would be a feature, and so is of course right off the
table for this release. Changing the error messages to be clearer should
be fine.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-04-17 18:28:18 | Re: utf8 COPY DELIMITER? |
| Previous Message | Andrew Dunstan | 2007-04-17 17:13:49 | Re: utf8 COPY DELIMITER? |