Re: pgsqODBC binding parameters II (fwd)

> > 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 ?

Yes, it does.

> What is a real cbValue(the 3rd parameter of SQLPutData) ?

I don't test it. I try it and note a message.

> And how does the above mylog() display in reality ?

I think (not sure):
DataPut other cbValue = 4, rgbValue = 4

> Are your paramters integers only ?

Unfortunately yes.

> Reading SQLPutData's spec together with SQLBindParameter's

Where can I find these spec?

> 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.

I copy it from string version and delete +1 (length).  I think this
is good way. Length can't be determined by the type.  CHAR or VARCHAR
could have different lengths.

Luf