| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>, Richard Hetherington <hetheringtonrichard(at)hotmail(dot)com> |
| Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: ADO CommandTimeout vs Postgres statement_timeout parameter |
| Date: | 2016-05-30 01:24:16 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1F57B9C6@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
From: Inoue, Hiroshi [mailto:h-inoue(at)dream(dot)email(dot)ne(dot)jp]
What does SQL_QUERY_TIMEOUT means for e.g.SQLBulkOperations()?
The ODBC spec doesn’t seem to specify it. The SQL_ATTR_QUERY_TIMEOUT description in the SQLSetStmtAttr() reference page mentions “SQL Statement”, whereas SQLBulkOperations() talks about “operations.” And the relationship between SQL statements and operations is not specified. I think that depends on the driver, and it’s legal that the query timeout applies to each operation.
Apart from that, I forgot to call QR_Destructor() after CC_send_query(). Revised patch attached.
Regards
Takayuki Tsunakawa
| Attachment | Content-Type | Size |
|---|---|---|
| query_timeout_v2.patch | application/octet-stream | 10.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Venkatesan, Sekhar | 2016-05-30 04:59:54 | Re: PostgreSQL: SQLSetPos fails with SetPos update return error. |
| Previous Message | Tsunakawa, Takayuki | 2016-05-30 01:13:17 | Re: [patch] fix buffer overrun in logging, and code cleanup |