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 0A3221C70F24FB45833433255569204D1F57B9C6@G01JPEXMBYT05
Whole thread Raw
In response to Re: ADO CommandTimeout vs Postgres statement_timeout parameter  ("Inoue, Hiroshi" <h-inoue@dream.email.ne.jp>)
List pgsql-odbc

From: Inoue, Hiroshi [mailto:h-inoue@dream.email.ne.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

pgsql-odbc by date:

Previous
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: [patch] fix buffer overrun in logging, and code cleanup
Next
From: "Venkatesan, Sekhar"
Date:
Subject: Re: PostgreSQL: SQLSetPos fails with SetPos update return error.