Re: Unicode/client_encoding/conversion problem
От | Dave Page |
---|---|
Тема | Re: Unicode/client_encoding/conversion problem |
Дата | |
Msg-id | 03AF4E498C591348A42FC93DEA9661B844B0A0@mail.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Unicode/client_encoding/conversion problem (Andreas Pflug <Andreas.Pflug@web.de>) |
Ответы |
Re: Unicode/client_encoding/conversion problem
|
Список | 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.Pflug@web.de] > Sent: 16 June 2003 11:52 > To: pgsql-odbc@postgresql.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 >
В списке pgsql-odbc по дате отправления: