Re: ADO CommandTimeout vs Postgres statement_timeout parameter - Mailing list pgsql-odbc

From Tsunakawa, Takayuki
Subject Re: ADO CommandTimeout vs Postgres statement_timeout parameter
Date
Msg-id 0A3221C70F24FB45833433255569204D1F57749A@G01JPEXMBYT05
Whole thread Raw
In response to ADO CommandTimeout vs Postgres statement_timeout parameter  (Richard Hetherington <hetheringtonrichard@hotmail.com>)
List pgsql-odbc

From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Richard Hetherington

Hi, I have been debugging why the ADO CommandTimeout property has no effect on Postgres Queries and I believe that it is being ignored. Is this something that could be modified in a future ODBC Driver release. What I would like to see is an auto prepending of this value to a SQL Query being passed in if set.

 

 

I guess you are right.  The current psqlODBC does not implement SQLSetConnectAttr/SQLSetStmtAttr(SQL_QUERY_TIMEOUT) and do nothing when it is called, as follows:

 

                         case SQL_QUERY_TIMEOUT:            /* ignored */

                                       mylog("SetStmtOption: SQL_QUERY_TIMEOUT, vParam = " FORMAT_LEN "\n", vParam);

                                       /* "0" returned in SQLGetStmtOption */

                                       break;

 

 

But I don't know whether setting ADO's CommandTimeout leads to setting SQL_QUERY_TIMEOUT.  Could you show us the MyLog output of psqlODBC to confirm that?

 

Regards

Takayuki Tsunakawa

pgsql-odbc by date:

Previous
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: PostgreSQL: SQLSetPos fails with SetPos update return error.
Next
From: "Inoue, Hiroshi"
Date:
Subject: Re: PostgreSQL: SQLSetPos fails with SetPos update return error.