Using CommandTimeout makes PostgreSQLDirect .NET stop working
Posted: Tue 17 Apr 2007 07:52
Hello,
When I execute a query that takes longer time than what is specified in the DbCommand.CommandTimeout property, I get a System.ArgumentOutOfRangeException exception saying:
"System.ArgumentOutOfRangeException: Non-negative number required.
Parameter name: count"
Then, it seems like the entire PostgreSQLDirect .NET module stops working and any subsequent query fails.
I do not want to disable DbCommand.CommandTimeout by setting it to zero or to a huge number, because I need to know when a query takes too long to execute.
Will this problem be fixed in future versions? Is there a workaround that I ca use while waiting for a bug fix?
Regards,
Per
When I execute a query that takes longer time than what is specified in the DbCommand.CommandTimeout property, I get a System.ArgumentOutOfRangeException exception saying:
"System.ArgumentOutOfRangeException: Non-negative number required.
Parameter name: count"
Then, it seems like the entire PostgreSQLDirect .NET module stops working and any subsequent query fails.
I do not want to disable DbCommand.CommandTimeout by setting it to zero or to a huge number, because I need to know when a query takes too long to execute.
Will this problem be fixed in future versions? Is there a workaround that I ca use while waiting for a bug fix?
Regards,
Per