Re: Problem with client_encoding and PsqlODBC driver.

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Kadri Raudsepp <raudsepp(dot)kadri(at)gmail(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Problem with client_encoding and PsqlODBC driver.
Date: 2015-03-20 19:27:59
Message-ID: 550C74BF.9050703@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

On 03/20/2015 11:10 AM, Kadri Raudsepp wrote:
> Thank you for trying to help, Adrian :)
>
> The links you sent I have already seen, no help unfortunately. I have
> dug deep into SQL Server's soul and system tables and system
> configuration and procedures and functions and anything I could think
> of. I'm quite convinced by now that my issue is impossible to solve from
> the SQL Server end and apart from the PgAdmin solution for getting the
> correct characters in my data which requires a lot of additional steps
> and time, the only hope is in the odbc driver itself, getting it somehow
> not to override my latin1 client_encoding.

I don't think it is. From the results you show most of the characters
display correctly. This seems to me that the encoding on the receiving
end is close but not an exact match. The only thing I have left to
suggest is the MS ODBC Test utility:

https://msdn.microsoft.com/en-us/library/ms712676%28v=vs.85%29.aspx

Maybe getting closer to a raw connection will help id the problem.

>
> Thank you again and have a nice weekend!
> Katie
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Lindsay Stevens 2015-03-23 06:51:46 Re: Re: Is it possible to set psql connection parameters before an ODBC connection?
Previous Message Kadri Raudsepp 2015-03-20 18:10:55 Re: Problem with client_encoding and PsqlODBC driver.