| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Chuck McDevitt <cmcdevitt(at)greenplum(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UTF8 with BOM support in psql |
| Date: | 2009-11-17 18:22:24 |
| Message-ID: | 4B02E9E0.1010906@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Peter Eisentraut wrote:
>>
>>> Well, someone could implement UTF-16 or UTF-whatever as client encoding.
>>> But I have not heard of any concrete proposals about that.
>>>
>
>
>> Doesn't the nul byte problem make that seriously hard?
>>
>
> Just about impossible. It would require a protocol bump, and removal of
> C-style string usage *everywhere* on the client side.
>
> Again, this is something that might be more feasible with encoding
> conversion inside psql --- translating UTF16 to UTF8 immediately upon
> reading it from any external file would confine the problem to possibly
> manageable bounds.
>
>
>
Well, it might be a good idea to provide at least some support in libpq.
Making each client do it from scratch seems a bit inefficient.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2009-11-17 18:39:46 | Re: actualised funcs typmod patch |
| Previous Message | Tom Lane | 2009-11-17 18:01:52 | Re: UTF8 with BOM support in psql |