Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Arno Welzel <usenet@arnowelzel.de>
Newsgroups: comp.lang.php
Subject: Re: odbc with unicode support
Date: Tue, 20 Nov 2018 09:22:52 +0100
Lines: 28
Message-ID: <g5huiuFb3ugU1@mid.individual.net>
References: <p6PID.256320$1C7.180194@usenetxs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net XwwFnAyIaW249AGIkAMaWAZtaYMV8gCG1feIpPjfJIeN72c3WZ
Cancel-Lock: sha1:/UjQEQdcQirhfYus3IP208XzKwE=
Openpgp: preference=signencrypt
In-Reply-To: <p6PID.256320$1C7.180194@usenetxs.com>
Xref: csiph.com comp.lang.php:17830

Jos Geerts:

> Hi all,
> 
> Is it a big effort to change the existing odbc driver to support
> unicode (I need this to access databases with unicode data - chinese,
> japanse, cyrillic - character sets?
> 
> Currently the driver/extention automatically change the data to ansi
> characterset, and that makes the data unusable as the data cannot be
> converted from multibytes to just a single byte.
> 
> I did try to cast the data as "binary" and that worked, I retrieved
> the data as-is, no conversion was done, so the unicode data was
> complete. The problem is that not all sql languages support binary
> (Impala SQL does not support it), so it's not always possible to cast
> the data as binary.
> 
> So I'm a bit stuck here... :-(

Maybe this helps:

<https://www.easysoft.com/support/kb/kb01072.html>


-- 
Arno Welzel
https://arnowelzel.de