ODBC SQLNumResultCols broken?

The ODBC book I have claims that if, after execution, a statement
has no result data, then SQLNumResultCols(statement, &ncols) returns
ncols == 0.  TRUE?  FALSE?

If TRUE, then postgresql ODBC driver (latest stuff) is broken because
it always returns the number of '?' there are in the SQL query
statement no matter if any rows were returned by the execute.

What I am really trying to do is test existence of an index "id" in a table.
I call SQLExecute() on a prepared statement that looks like this:
"select id from tablename where id = ?"
Parameter is bound, everything returns success.  Now I can tell if
the id is in the table if any rows were returned from this query.  Is
there some other or better way to do this?

Of course, postgresql ODBC and JDBC drivers are still broken in the
ways I have reported before, but no one seems to care.  8^(

Bill <bouma@cplane.com>