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

RE: pgsqODBC binding parameters II (fwd)

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Ludek Finstrle" <xfinstrl(at)informatics(dot)muni(dot)cz>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: RE: pgsqODBC binding parameters II (fwd)
Date: 2001-03-24 02:31:51
Message-ID: EKEJJICOHDIEMGPNIFIJKEBHDPAA.Inoue@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
> -----Original Message-----
> From: Ludek Finstrle [mailto:xfinstrl(at)informatics(dot)muni(dot)cz]
> 
> I apllied your tips and patch now looks:
> 

> diff -iwaru postsrc-orig/execute.c postsrc-patched/execute.c
> --- postsrc-orig/execute.c	Fri Mar 23 10:37:47 2001
> +++ postsrc-patched/execute.c	Fri Mar 23 10:55:56 2001
> @@ -778,33 +778,46 @@

[snip]

> +			else
> +			{
> +				mylog("DataPut other cbValue = %d, 
> rgbValue = %l d\n",current_param->buflen,*((SDWORD *) rgbValue));
> +				current_param->EXEC_buffer = 
> malloc(current_param->buflen);

Does SQLPutData() come to this place in your test case ?
What is a real cbValue(the 3rd parameter of SQLPutData) ?
And how does the above mylog() display in reality ?
Are your paramters integers only ?

Reading SQLPutData's spec together with SQLBindParameter's
one, I couldn't find any description that the 9-th parameter of
SQLBindParameter could specifiy the SQLPutData's data length.
According to SQLPutData's spec, the length seems to be 
determined by the type of the parameter though I'm not sure.

regards,
Hiroshi Inoue 

In response to

Responses

pgsql-odbc by date

Next:From: Larry RosenmanDate: 2001-03-24 16:28:24
Subject: Re: odbc/UnixWare 7.1.1: No Go.
Previous:From: Larry RosenmanDate: 2001-03-23 22:58:56
Subject: Re: odbc/UnixWare 7.1.1: No Go.

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