| From: | "Matsumura, Ryo" <matsumura(dot)ryo(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Nagaura, Ryohei" <nagaura(dot)ryohei(at)jp(dot)fujitsu(dot)com> |
| Cc: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "'jingwangian(at)gmail(dot)com'" <jingwangian(at)gmail(dot)com>, "'michael(dot)paquier(at)gmail(dot)com'" <michael(dot)paquier(at)gmail(dot)com>, "'meskes(at)postgresql(dot)org'" <meskes(at)postgresql(dot)org>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: [suggestion]support UNICODE host variables in ECPG |
| Date: | 2018-12-25 05:07:28 |
| Message-ID: | 03040DFF97E6E54E88D3BFEE5F5480F737A80E2F@G01JPEXMBYT04 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> * What's the benefit of supporting UTF16 in host variables?
I think that the first benefit of suggestion is providing a way to
treat UTF16 chars for application. Whether or not to support above
U+FFFF (e.g. surrogate pair) may be a next discussion.
For that purpose, implementation for the suggestion may be easier
than for supporting UTF16 at client_encoding. Uvarchar seems to be
a label indicating that stored data is encoded by UTF16. It localizes
the impacts within only labeled host variable.
# At least, ecpglib is not good at treating 0x00 as a part of one character.
Regards
Ryo Matsumura
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-12-25 05:27:03 | Re: Tab completion for ALTER INDEX|TABLE ALTER COLUMN SET STATISTICS |
| Previous Message | Iwata, Aya | 2018-12-25 04:53:13 | RE: libpq debug log |