Re: Unicode/client_encoding/conversion problem - Mailing list pgsql-odbc

From Dave Page
Subject Re: Unicode/client_encoding/conversion problem
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B844B0A6@mail.vale-housing.co.uk
Whole thread Raw
In response to Unicode/client_encoding/conversion problem  (Andreas Pflug <Andreas.Pflug@web.de>)
List pgsql-odbc

> -----Original Message-----
> From: Andreas Pflug [mailto:Andreas.Pflug@web.de]
> Sent: 18 June 2003 14:22
> To: Dave Page
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: Unicode/client_encoding/conversion problem
>
>
> Dave Page wrote:
>
> >Thanks, committed with minor fix to close the comment in the correct
> >place (pls check).
> >
> >
> >
>
> Hi Dave,
>
> fix hasn't  made it correctly into the source. The comment
> was just to
> leave the old code for reference. This probably happened because the
> second fix (ResolveNumeric)  would shift the rows of the first fix.
>
> There's no switch(param_sqltype) needed, instead all code
> that's under
> the 3 case SQL_xxx is to be executed for unicode. Absolutely wrong is
> the last line "buf=buffer" in the default hieve, because this would
> override the previous conversion.
>
> Attached a new patch file, diff'd from the current cvs.

Ahh yes, that makes more sense. Applied.

Regards, Dave.

pgsql-odbc by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: Unicode/client_encoding/conversion problem
Next
From: Tim Woodall
Date:
Subject: Re: Bug in ODBC driver doing UPDATES and DELETES