Re: client encoding mismatch - Mailing list pgsql-odbc

From Hiroshi Saito
Subject Re: client encoding mismatch
Date
Msg-id 032801c5bf75$7563a2b0$01324d80@hiroshi5jz7dqj
Whole thread Raw
In response to Re: client encoding mismatch  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgsql-odbc
Hi.

I tell that it is satisfactory.

[3624]PDATA_free_params:  ENTER, self=186673392
[3624]**** PGAPI_ExecDirect: hstmt=186672968, statement='set client_encoding to 'WIN1251''
[3624]PGAPI_ExecDirect: calling PGAPI_Execute...
[3624]PGAPI_Execute: entering...
[3624]PGAPI_Execute: clear errors...
[3624]recycle statement: self= 186672968
[3624]PDATA_free_params:  ENTER, self=186673392
[3624]Exec_with_parameters_resolved: copying statement params: trans_status=1, len=32,
stmt='set client_encoding to 'WIN1251''
[3624]   stmt_with_params = 'set client_encoding to 'WIN1251''
[3624]      it's NOT a select statement: stmt=186672968
[3624]send_query(): conn=186661696, query='set client_encoding to 'WIN1251''
[3624]in QR_Constructor
[3624]exit QR_Constructor
[3624]the server returned the error: ERROR:  conversion between WIN1251 and EUC_JP is not
supported
[3624]send_query: done sending query
[3624]QR_fetch_tuples: cursor = '', self->cursor=0

> > conn_settings='' conn_encoding='WIN'
> >
>
> Hmm, how odd. It works for me. I assume you are using the ANSI driver?
>
> Hiroshi - can you use win1251 with your patch?
>

Please carry out by the method of not setting option.

Regards,
Horoshi Saito



pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: client encoding mismatch
Next
From: "Hiroshi Saito"
Date:
Subject: Re: client encoding mismatch