This did not cause a problem before since it was ignored. So, if a user application did not set any timeout it was implicitly set to 30 seconds. ADO has this feature to set the timeout by default to 30 seconds. The problem happens with ADO applications with no query timeout setting. Those who do not want any timeout in the application, do not need to do anything to their applications and run as they used to. The support for this ODBC feature started in Pervasive.SQL V8. The timeout is specified as a statement option. If it is specified, the engine will stop processing any query that is taking more than the timeout value. ODBC standards provide a way to specify query timeout. If a query's processing time was too long, there was no way to stop the processing. Prior to Pervasive.SQL V8, query timeouts were not checked by the ODBC engine. Query Timeout error is due to support for SQL_QUERY_TIMEOUT API in V8.ĮRROR [ODBC Engine Queries timeout due to support for the SQL_QUERY_TIMEOUT API in Pervasive.SQL V 8.Īpplications working with Pervasive.SQL 2000 no longer work with Pervasive.SQL V8. How to make Pervasive.SQL V8 engine ignore SQL_QUERY_TIMEOUT API ![]() Also, how long does the query take through the PCC? What version of Pervasive.SQL are you using?You can also use the PsqlConnection ConnectionTimeout property to increase (or eliminate the timeout by setting to 0).
0 Comments
Leave a Reply. |