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.

Regards,
Andreas