odbc problem on Japanese windows machine

This is a multi-part message in MIME format.

------_=_NextPart_001_01C83D8F.4AF118C7
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I am trying to use postgres odbc driver on windows Japanese machine, to
test connection to a remote postgres database. The database has latin1
encoding.

Connection tests to databases with latin1 encoding fail with this error
message:

fatal: conversion between SJIS and LATIN1 is not supported

Connection tests to databases with utf8 encoding succeed.

I checked both server source and odbc driver source and saw that the
message comes from postgres server code.

It seems that the postgres odbc sends SJIS characters to the latin1
database and it cannot convert.

I know that the next command retrieves with the same error:

alter database <db_name> set client_encoding=3D"SJIS"

Is there any switch in the code to bypass local machine encoding?

Why does it send Japanese encoding?

Postgres odbc driver is not Japanese application. For what the
conversion is needed?

Is there any way to overcome this problem?

Steps to reproduce error message:

1. Put postgres odbc drivers (psqlodbc30a.dll and psqlodbc35w.dll) under
c:\windows\system32

2. Update machine registry with next values:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]

"PostgreSQL ANSI"=3D"Installed"

"PostgreSQL Unicode"=3D"Installed"

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\PostgreSQL ANSI]

"APILevel"=3D"1"

"ConnectFunctions"=3D"YYN"

"Driver"=3D"c:\windows\system32\PSQLODBC30A.DLL"

"DriverODBCVer"=3D"03.00"

"FileUsage"=3D"0"

"Setup"=3D" c:\windows\system32\PSQLODBC30A.DLL"

"SQLLevel"=3D"1"

"UsageCount"=3Ddword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\PostgreSQL Unicode]

"APILevel"=3D"1"

"ConnectFunctions"=3D"YYN"

"Driver"=3D" c:\windows\system32\PSQLODBC35W.DLL"

"DriverODBCVer"=3D"03.51"

"FileUsage"=3D"0"

"Setup"=3D" c:\windows\system32\PSQLODBC35W.DLL"

"SQLLevel"=3D"1"

"UsageCount"=3Ddword:00000001

3. Create datasource and test connection to latin1 encoding database:

Settings -> administrative tools -> data source (ODBC)

And then add system data source with postgres driver. Configure this
data source to

connect to latin1 postgres database.

Thanks,

Yuval Sofer
BMC Software
CTM&D Business Unit

DBA Team
972-52-4286-282
yuval_sofer [at] bmc.com <mailto:yuval_sofer [at] bmc.com>

Yuval Sofer
BMC Software
CTM&D Business Unit

DBA Team
972-52-4286-282
yuval_sofer [at] bmc.com

------_=_NextPart_001_01C83D8F.4AF118C7
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>

</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

Hi, <o:p></o:p>

<o:p> </o:p>

I am trying to use postgres odbc =
driver on
windows Japanese machine, to test connection to a remote postgres =
database. The
database has latin1 encoding. <o:p></o:p>

<o:p> </o:p>

Connection tests to databases with =
latin1
encoding fail with this error message: <o:p></o:p>

<o:p> </o:p>

fatal: conversion between SJIS and =
LATIN1
is not supported<o:p></o:p>

<o:p> </o:p>

Connection tests to databases with =
utf8
encoding succeed.<o:p></o:p>

<o:p> </o:p>

I checked both server source and =
odbc
driver source and saw that the message comes from postgres server code. =
<o:p></o:p>

<o:p> </o:p>

It seems that the postgres odbc =
sends SJIS
characters to the latin1 database and it cannot =
convert.<o:p></o:p>

I know that the next command =
retrieves
with the same error: <o:p></o:p>

<o:p> </o:p>

alter database <db_name> set
client_encoding=3D"SJIS"<o:p></o:p>

<o:p> </o:p>

Is there any switch in the code to =
bypass
local machine encoding?<o:p></o:p>

Why does it send Japanese encoding? =
<o:p></o:p>

Postgres odbc driver is not =
Japanese
application. For what the conversion is needed? =
<o:p></o:p>

Is there any way to overcome this =
problem?
<o:p></o:p>

<o:p> </o:p>

Step s to =
reproduce error
message: <o:p></o:p>

<o:p> </o:p>

1. Put postgres odbc drivers
(psqlodbc30a.dll and psqlodbc35w.dll) under =
c:\windows\system32<o:p></o:p>

<o:p> </o:p>

2. Update machine registry with =
next
values: <o:p></o:p>

[HKEY_LOCAL_MACHINE\SOF TWARE\ODBC\OD=
BCINST.INI\ODBC
Drivers]<o:p></o:p>

"PostgreSQL
ANSI"=3D"Installed"<o:p></o:p>

"PostgreSQL
Unicode"=3D"Installed"<o:p></o:p>

<o:p> </o:p>

[HKEY_LOCAL_MACHINE\SOF TWARE\ODBC\OD=
BCINST.INI\PostgreSQL
ANSI]<o:p></o:p>

"APILevel"=3D"1"=
<o:p></o:p>

"ConnectFunctions"=3D"=
;YYN"<o:p></o:p>

"Driver"=3D"c:\window=
s\system32\PSQLODBC30A.DLL"<o:p></o:p>

"DriverODBCVer"=3D"03=
..00"<o:p></o:p>

"FileUsage"=3D"0"=
;<o:p></o:p>

"Setup"=3D"
c:\windows\system32\PSQLODBC30A.DLL"<o:p></o:p>

"SQLLevel"=3D"1"=
<o:p></o:p>

"UsageCount"=3Ddword:00000=
001<o:p></o:p>

<o:p> </o:p>

[HKEY_LOCAL_MACHINE\SOF TWARE\ODBC\OD=
BCINST.INI\PostgreSQL
Unicode]<o:p></o:p>

"APILevel"=3D"1"=
<o:p></o:p>

"ConnectFunctions"=3D"=
;YYN"<o:p></o:p>

"Driver"=3D"
c:\windows\system32\PSQLODBC35W.DLL"<o:p></o:p>

"DriverODBCVer"=3D"03=
..51"<o:p></o:p>

"FileUsage"=3D"0"=
;<o:p></o:p>

"Setup"=3D"
c:\windows\system32\PSQLODBC35W.DLL"<o:p></o:p>

"SQLLevel"=3D"1"=
<o:p></o:p>

"UsageCount"=3Ddword:00000=
001<o:p></o:p>

<o:p> </o:p>

3. Create datasource and test =
connection
to latin1 encoding database: <o:p></o:p>

Settings -> administrative tools =
->
data source (ODBC) <o:p></o:p>

And then add system data source =
with
postgres driver. Configure this data source to =
<o:p></o:p>

connect to latin1 postgres =
database.<o:p></o:p>

<o:p> </o:p>

Thanks, =
<o:p></o:p>

<o:p> </o:p>

Yuval Sofer 
BMC Software 
CTM&D Business Unit<o:p></o:p>

DBA Team 
972-52-4286-282 
<a href=3D"mailto:yuval_sofer [at] bmc.com" =
title=3D"mailto:yuval_sofer [at] bmc.com">yuval_sofer [at] bmc.com</a><o:p></o=
:p>

<o:p> </o:p>

<o:p> </o:p>

<o:p> </o:p>

Yuval Sofer 
BMC Software 
CTM&D Business Unit<o:p></o:p>

DBA Team 
972-52-4286-282 
<a =
href=3D"mailto:yuval_sofer [at] bmc.com">yuval_sofer [at] bmc.com</a>=
<o:p></o:p></p=
>

<o:p> </o:p>

</div>

</body>

</html>

------_=_NextPart_001_01C83D8F.4AF118C7--

Yuval_Sofer [ Do, 13 Dezember 2007 14:51 ] [ ID #1888961 ]

Re: odbc problem on Japanese windows machine

Hi.

Sorry late reaction...
It is the conversion which is not supported by PostgreSQL. It does not have
the conversion definition between LATIN1 and SJIS.
See,
http://www.postgresql.org/docs/8.2/static/multibyte.html#AEN 24142

Regards,
Hiroshi Saito

----- Original Message -----
From: Sofer, Yuval
To: pgsql-odbc [at] postgresql.org
Sent: Thursday, December 13, 2007 10:51 PM
Subject: [ODBC] odbc problem on Japanese windows machine

Hi,

I am trying to use postgres odbc driver on windows Japanese machine, to test connection to a
remote postgres database. The database has latin1 encoding.

Connection tests to databases with latin1 encoding fail with this error message:

fatal: conversion between SJIS and LATIN1 is not supported

Connection tests to databases with utf8 encoding succeed.

I checked both server source and odbc driver source and saw that the message comes from
postgres server code.

It seems that the postgres odbc sends SJIS characters to the latin1 database and it cannot
convert.
I know that the next command retrieves with the same error:

alter database <db_name> set client_encoding="SJIS"

Is there any switch in the code to bypass local machine encoding?
Why does it send Japanese encoding?
Postgres odbc driver is not Japanese application. For what the conversion is needed?
Is there any way to overcome this problem?

Steps to reproduce error message:

1. Put postgres odbc drivers (psqlodbc30a.dll and psqlodbc35w.dll) under c:\windows\system32

2. Update machine registry with next values:
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
"PostgreSQL ANSI"="Installed"
"PostgreSQL Unicode"="Installed"

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\PostgreSQL ANSI]
"APILevel"="1"
"ConnectFunctions"="YYN"
"Driver"="c:\windows\system32\PSQLODBC30A.DLL"
"DriverODBCVer"="03.00"
"FileUsage"="0"
"Setup"=" c:\windows\system32\PSQLODBC30A.DLL"
"SQLLevel"="1"
"UsageCount"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\PostgreSQL Unicode]
"APILevel"="1"
"ConnectFunctions"="YYN"
"Driver"=" c:\windows\system32\PSQLODBC35W.DLL"
"DriverODBCVer"="03.51"
"FileUsage"="0"
"Setup"=" c:\windows\system32\PSQLODBC35W.DLL"
"SQLLevel"="1"
"UsageCount"=dword:00000001

3. Create datasource and test connection to latin1 encoding database:
Settings -> administrative tools -> data source (ODBC)
And then add system data source with postgres driver. Configure this data source to
connect to latin1 postgres database.

Thanks,

Yuval Sofer
BMC Software
CTM&D Business Unit
DBA Team
972-52-4286-282
yuval_sofer [at] bmc.com

Yuval Sofer
BMC Software
CTM&D Business Unit
DBA Team
972-52-4286-282
yuval_sofer [at] bmc.com

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Hiroshi Saito [ Fr, 14 Dezember 2007 07:35 ] [ ID #1889069 ]

Re: odbc problem on Japanese windows machine

Sofer, Yuval wrote:
> Hi,
>
> I am trying to use postgres odbc driver on windows Japanese machine, to
> test connection to a remote postgres database. The database has latin1
> encoding.
>
> Connection tests to databases with latin1 encoding fail with this error
> message:
>
> fatal: conversion between SJIS and LATIN1 is not supported

Are you testing the ANSI version driver ?
If so, please set the *Connect Settings* option like
set client_encoding to 'XXXX'
(XXXX e.g. SQL_ASCII, LATIN1 etc).

You can see the example (SJIS case) at
http://www.geocities.jp/inocchichichi/psqlodbc/encoding.jpg .

However I'm not sure if you can see LATIN1 specific characters using
Japanese machine.

regards,
Hiroshi Inoue

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Hiroshi Inoue [ Fr, 14 Dezember 2007 09:14 ] [ ID #1889070 ]

Re: odbc problem on Japanese windows machine

Hi,
Thanks you very much ! you solution did it.
Regards
Yuval

-----Original Message-----
From: Hiroshi Inoue [mailto:inoue [at] tpf.co.jp]
Sent: Friday, December 14, 2007 10:15 AM
To: Sofer, Yuval
Cc: pgsql-odbc [at] postgresql.org
Subject: Re: [ODBC] odbc problem on Japanese windows machine

Sofer, Yuval wrote:
> Hi,
>
> I am trying to use postgres odbc driver on windows Japanese machine,
to
> test connection to a remote postgres database. The database has latin1

> encoding.
>
> Connection tests to databases with latin1 encoding fail with this
error
> message:
>
> fatal: conversion between SJIS and LATIN1 is not supported

Are you testing the ANSI version driver ?
If so, please set the *Connect Settings* option like
set client_encoding to 'XXXX'
(XXXX e.g. SQL_ASCII, LATIN1 etc).

You can see the example (SJIS case) at
http://www.geocities.jp/inocchichichi/psqlodbc/encoding.jpg .

However I'm not sure if you can see LATIN1 specific characters using
Japanese machine.

regards,
Hiroshi Inoue

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Yuval_Sofer [ So, 16 Dezember 2007 12:53 ] [ ID #1889184 ]