Re: FW: Varchar parameter conversion

[Andrei Kovalevski <andyk(at)commandprompt(dot)com>]

Hello,

I'm not so sure what is going on, unicode version of driver should 
provide internal conversion to UTF-8, but value in log file doesn't look 
as a valid UTF-8 string:
-!-"-#-$-%-&-''-(-)-*-+-,---.-/-0-1-2-3-4-5-6-7-8-9-:-;-<-=->-?-(at)-A-B-C-D-E-F-G-H-I-J-K-L-M-N-O-P-Q-R-S-T-U-V-W-X-Y-Z-[-\\-]-^-_-`-a-b-c-d-e-f-g-h-i-j-k-l-m-n-o-p-q-r-s-t-u-v-w-x-y-z-{-|-}-~--Ђ-Ѓ-‚-ѓ-„-…-†
-‡-€-‰-Љ-‹-Њ-Ќ-Ћ-Џ-ђ-‘-’-“-”-•-–-—-˜-™-љ-›-њ-ќ-ћ-џ- 
-Ў-ў-Ј-¤-Ґ-¦-§-Ё-©-Є-«-¬-­-®-Ї-°-±-І-і-ґ-µ-¶-·-ё-№-є-»-ј-Ѕ-ѕ-ї-А-Б-В-Г-Д-Е-Ж-З-И-Й-К-Л-М-Н-О-П-Р
-РЎ-Рў-РЈ-Р¤-РҐ-Р¦-Р§-РЁ-Р©-РЄ-Р«-Р¬-Р­-Р®-РЇ-Р°-Р±-РІ-Рі-Рґ-Рµ-Р¶-Р·-Рё-Р№-Рє-Р»-Рј-РЅ-Рѕ-Рї-СЂ-СЃ-С‚-Сѓ-С„-С…-С†-С‡-С€-С‰-СЉ-С‹-СЊ-СЌ-СЋ-СЏ--------

It looks like you are passing wide string as the first parameter. You 
can post here your code, where you prepare this string before placing it 
into the inbound buffer. More simple way to confirm this version - 
replace SQL_C_CHAR with SQL_C_WCHAR in SQLBindParameters.

And of course you can try other PostgreSQL ODBC drivers, for example:
https://projects.commandprompt.com/public/odbcng/wiki/Downloads

Zubkovsky, Sergey wrote:
> Sorry, I forgot to attach the log file.
>
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Zubkovsky, Sergey
> Sent: Tuesday, July 24, 2007 3:37 PM
> To: Andrei Kovalevski
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Varchar parameter conversion
>
> Hello,
>
> Thank you for your answer!
> But this is the same what I do exactly.
>
> I have realized the stored procedure call with a varchar parameter value
> which originally contained characters with the ASC-codes from 1 to 255.
> For visualization purpose all these chars were separated by char '-'.
>
> A log file was produced by the ODBC driver is attached.
>
> Look at the "GetPartitionName_sp" stored procedure call.
> I suppose that the first parameter was converted to UTF-8.
> But I didn't do this conversion!
>
>
> -----Original Message-----
> From: Andrei Kovalevski [mailto:andyk(at)commandprompt(dot)com] 
> Sent: Monday, July 23, 2007 6:41 PM
> To: Zubkovsky, Sergey
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Varchar parameter conversion
>
> Hello,
>
> Try to use statements with parameters:
> SQLBindParameters(stmt, 1, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_VARCHAR, 
> query_length, 0, param_ptr, query_length, buff_ptr);
> SQLExecDirect(stmt, "{call SomeProc(?}}");
>
> Zubkovsky, Sergey wrote:
>   
> > Hello,
> >
> > My client program is developed on C++ & ODBC.
> >
> > It's a Windows Unicode application.
> >
> > I'm trying to pass a "varchar" parameter value to a user-defined 
> > stored procedure.
> >
> > Each character of this actual parameter value (which ASC code is 
> > greater than 127) is transformed into some two chars.
> >
> > This value is stored and bound as a non-Unicode string (traditional 
> > C-string) in the program.
> >
> > So, some conversion happens for these characters.
> >
> > It seems to me that it's the ODBC driver's intervention.
> >
> > Is that right?
> >
> > And how can I avoid this unwanted conversion?
> >
> > Additional environment info:
> >
> > OS: Windows XP SP2
> >
> > PostgreSQL version: "PostgreSQL 8.2.4 on i686-pc-mingw32, compiled by 
> > GCC gcc.exe (GCC) 3.4.2 (mingw-special)"
> >
> > ODBC driver version: PostgreSQL Unicode 8.02.04.00
> >
> > SHOW server_encoding;
> >
> > "SQL_ASCII"
> >
> > SHOW client_encoding;
> >
> > "SQL_ASCII"
> >
> > Thank you.
> >     
Andrei.