ODBC Error on single table "No columns were bound prior to calling SQLFetch"

Question

Question

Katrina E Rodenhaus · Oct 26, 2023

#Beginner #ODBC #SQL #InterSystems IRIS #InterSystems IRIS for Health

I am very new to IRIS. We are developing a PHP application that connects to an IRIS instance of one of our vendors. I am having trouble with a specific table. When I need to query this specific table for specific fields, I am receiving an error. However, if I change the call to get all columns (`*`), there is no error. I get 37K records returned.

Error:

PHP Fatal error:  Uncaught PDOException: SQLSTATE[SL009]: <<Unknown error>>: [unixODBC][Driver Manager]No columns were bound prior to calling SQLFetch or SQLFetchScroll (SQLFetchScroll[0] at /builddir/build/BUILD/php-8.1.20/ext/pdo_odbc/odbc_stmt.c:547) in test.php:187
Stack trace:
#0 IRIS.php(187): PDOStatement->fetchAll(2)
#1 test.php(20): Models\Db\AthenaIRIS::getRecords('HPA', 'FeeScheduleTxn', Array)
#2 {main}
  thrown in IRIS.php on line 187

Query:

SELECT Id FROM HPA.FeeScheduleTxn

Digging on the internet produced this StackOverflow question, but there are no answers. Is anyone else experiencing a similar problem or is there a known solution to this issue?

Discussion (4)1

Log in or sign up to continue

score 0 · Answer 1 · 2023-10-26T15:32:34-04:00

I haven't touched PHP in a bit, but are you binding your columns? I seem to remember PHP things getting a little finicky about making sure you do that before you fetch if you were specifying columns in the query, but not if you were doing a select *.

score 0 · Answer 2 · 2023-10-26T16:31:40-04:00

I am not binding the columns because I'm using PDO fetch mode `FETCH_ASSOC` to cast the resulting object to an array.

Also I should've made this more clear, the exact same functionality works for all other IRIS queries I have. For example, the following query returns results properly:

SELECT Id, Name, Mnemonic, Type FROM Dict.VisitTypes;

Are there settings or anything configurable that could effect this on specific tables?

score 0 · Answer 3 · 2023-10-26T16:45:36-04:00

Yes, security settings can get down to a columnar level. Also, if what you're querying is a view rather than a table, or if the ID column is defined to be something other than ID, that column just might not exist.

Also for clarification, when you use the select *, are you getting an Id column in the resulting data?

score 0 · Answer 4 · 2023-10-27T09:45:50-04:00

Thank you for telling me about the security settings. That's helpful, I'm going to check on that.

I've confirmed this is a table and when I use `select *` I am getting the Id column back. I've also confirmed through documentation that Id is a column that exists and should be queryable.