Luf,

So, if SQLDescribeParam is not supported, how do you
know how big to make the buffers?

I assume everyone must either use a standard size for
all parameters or the caller must know the right size to
use.

I guess I'll have to add an optional call to my library to
override the buffer size after the statement has been
prepared.

Glenn Lawler
www.incodesystems.com


-----Original Message-----
From: Ludek Finstrle [SMTP:luf@pzkagis.cz]
Sent: Wednesday, June 07, 2006 2:24 PM
To: Glenn B. Lawler
Cc: 'PostgreSQL ODBC List'
Subject: Re: [ODBC] DescribParam

> When I call SQLDescribeParam using PostgreSQL ODBC Driver
> psqlodbc-08_02_0002 SQL_ERROR is the return code.

This API has never been supported. Why do you use it when psqlODBC
returns info that it doesn't support SQLDescribeParam?

> What I am trying to do with this call is determine the buffer size
> needed to allocate a buffer so I can call SQLBindParameter with
> a big enough buffer.

There is the problem that PgSQL backend doesn't support it before
execution (I haven't found another information yet).

> My only thought was to provide an override for this in my library
> to force the parameter size when the driver does not return it.

Maybe you may depend on other information like PostgreSQL driver, ...

> Does anyone have a better workaround for this?

Sorry, I don't have one.

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly