Skip site navigation (1) Skip section navigation (2)

Re: Unicode/client_encoding/conversion problem

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>,<pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Unicode/client_encoding/conversion problem
Date: 2003-06-18 12:59:16
Message-ID: 03AF4E498C591348A42FC93DEA9661B844B0A0@mail.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
Thanks, committed with minor fix to close the comment in the correct
place (pls check).

Regards, Dave.

> -----Original Message-----
> From: Andreas Pflug [mailto:Andreas(dot)Pflug(at)web(dot)de] 
> Sent: 16 June 2003 11:52
> To: pgsql-odbc(at)postgresql(dot)org; Dave Page
> Subject: Unicode/client_encoding/conversion problem
> 
> 
> Hi friends,
> 
> when a column SQL_C_CHAR is handled in ResolveOneParam, the 
> conversion 
> is coded dependent on param_sqltype. If a SQL_CHAR variable 
> is bound to 
> it, no conversion takes place, which is incorrect. ODBC architecture 
> assumes sqltype to be the server_encoding, but this is irrelevant for 
> pgsql. Instead, everything is done with client_encoding (anything but 
> UNICODE doesn't make sense here), so we need a conversion to UTF-8 in 
> any case.
> 
> I wonder if the other direction is handled correctly...
> 
> A patch is attached.
> 
> Regards,
> Andreas
> 

Responses

pgsql-odbc by date

Next:From: Dave PageDate: 2003-06-18 12:59:28
Subject: Re: ResolveNumericParam problem
Previous:From: Sam WilliamsDate: 2003-06-18 00:02:33
Subject:

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group