| From: | Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de> |
|---|---|
| To: | pgsql-odbc(at)postgresql(dot)org, Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Subject: | Unicode/client_encoding/conversion problem |
| Date: | 2003-06-16 10:52:27 |
| Message-ID: | 3EEDA16B.1010202@web.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hi friends,
when a column SQL_C_CHAR is handled in ResolveOneParam, the conversion
is coded dependent on param_sqltype. If a SQL_CHAR variable is bound to
it, no conversion takes place, which is incorrect. ODBC architecture
assumes sqltype to be the server_encoding, but this is irrelevant for
pgsql. Instead, everything is done with client_encoding (anything but
UNICODE doesn't make sense here), so we need a conversion to UTF-8 in
any case.
I wonder if the other direction is handled correctly...
A patch is attached.
Regards,
Andreas
| Attachment | Content-Type | Size |
|---|---|---|
| ResolveOneParam.patch | text/plain | 655 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2003-06-16 11:14:33 | ResolveNumericParam problem |
| Previous Message | Ferran Pegueroles | 2003-06-16 03:15:40 | Re: [Tiny-cobol-users] New compiler options RFC |