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>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Unicode/client_encoding/conversion problem
Date: 2003-06-18 13:25:13
Message-ID: 03AF4E498C591348A42FC93DEA9661B844B0A6@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: Andreas Pflug [mailto:Andreas(dot)Pflug(at)web(dot)de]
> Sent: 18 June 2003 14:22
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)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.

Browse pgsql-odbc by date

  From Date Subject
Next Message Tim Woodall 2003-06-18 13:30:54 Re: Bug in ODBC driver doing UPDATES and DELETES
Previous Message Andreas Pflug 2003-06-18 13:21:38 Re: Unicode/client_encoding/conversion problem