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

Re: Unicode/client_encoding/conversion problem

From: Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Unicode/client_encoding/conversion problem
Date: 2003-06-18 13:21:38
Message-ID: 3EF06762.6010507@web.de (view raw or flat)
Thread:
Lists: pgsql-odbc
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

Attachment: ResolveOneParam.patch
Description: text/plain (1.4 KB)

In response to

pgsql-odbc by date

Next:From: Dave PageDate: 2003-06-18 13:25:13
Subject: Re: Unicode/client_encoding/conversion problem
Previous:From: Dave PageDate: 2003-06-18 12:59:28
Subject: Re: ResolveNumericParam problem

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