| From: | "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | FAU <fau(at)email(dot)com> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: UNICODE |
| Date: | 2013-07-10 03:27:35 |
| Message-ID: | 51DCD4A7.4070404@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hi,
(2013/07/10 1:29), FAU wrote:
> Hello,
>
> I'm trying to understand how (unix)ODBC and psqlodbc work together
> regarding UNICODE.
>
> So from what I understand is that ODBC UNICODE is/was inherently
> UCS-2LE.
Currently UTF-16LE or UTF-16BE according to the endianness of the
machine.
> Does the UNICODE driver version (which is psqlodbcw.so I
> assume) expect/send UCS-2LE or (as I read somewhere) UTF-8, or does it
> expect/send whatever the back-end database is setup to?
The unicode driver expects UTF-16 not UTF-8.
If you are to pass/accept UTF-8 string parameters, use the ANSI
version of the driver and set client_encoding to 'UTF-8'.
> Does the driver work the same way on Win and GNU/Linux regarding
> UNICODE?
Yes.
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | FAU | 2013-07-10 04:17:23 | Re: UNICODE |
| Previous Message | FAU | 2013-07-09 16:29:02 | UNICODE |