| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | Richard Hetherington <hetheringtonrichard(at)hotmail(dot)com>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Cc: | "james(dot)willison(at)aztecretail(dot)co(dot)uk" <james(dot)willison(at)aztecretail(dot)co(dot)uk>, Brad Bence <brad(dot)bence(at)aztecretail(dot)co(dot)uk> |
| Subject: | Re: ADO CommandTimeout vs Postgres statement_timeout parameter |
| Date: | 2016-05-19 05:21:52 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1F57749A@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-owner(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Inoue, Hiroshi | 2016-05-20 11:28:58 | Re: PostgreSQL: SQLSetPos fails with SetPos update return error. |
| Previous Message | Tsunakawa, Takayuki | 2016-05-19 01:57:25 | Re: PostgreSQL: SQLSetPos fails with SetPos update return error. |