Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #17829 > unrolled thread
| Started by | "Jos Geerts" <jgeert1@its.jnj.com> |
|---|---|
| First post | 2018-11-20 08:56 +0100 |
| Last post | 2018-11-20 08:40 +0000 |
| Articles | 3 — 3 participants |
Back to article view | Back to comp.lang.php
odbc with unicode support "Jos Geerts" <jgeert1@its.jnj.com> - 2018-11-20 08:56 +0100
Re: odbc with unicode support Arno Welzel <usenet@arnowelzel.de> - 2018-11-20 09:22 +0100
Re: odbc with unicode support Jos Geerts <jgeert1@its.jnj.com> - 2018-11-20 08:40 +0000
| From | "Jos Geerts" <jgeert1@its.jnj.com> |
|---|---|
| Date | 2018-11-20 08:56 +0100 |
| Subject | odbc with unicode support |
| Message-ID | <p6PID.256320$1C7.180194@usenetxs.com> |
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... :-( Any help/ideas would be welcome. Thanks, --------------= Posted using GrabIt =---------------- ------= Binary Usenet downloading made easy =--------- -= Get GrabIt for free from http://www.shemes.com/ =-
[toc] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2018-11-20 09:22 +0100 |
| Message-ID | <g5huiuFb3ugU1@mid.individual.net> |
| In reply to | #17829 |
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
[toc] | [prev] | [next] | [standalone]
| From | Jos Geerts <jgeert1@its.jnj.com> |
|---|---|
| Date | 2018-11-20 08:40 +0000 |
| Message-ID | <dMPID.227315$e55.159952@usenetxs.com> |
| In reply to | #17830 |
On Tue, 20 Nov 2018 09:22:52 +0100, Arno Welzel wrote: > 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> I already have seen/read that article, and yes it provides some workarounds. But it's not solving my problem.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.php
csiph-web