Using CommandTimeout makes PostgreSQLDirect .NET stop working

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Post Reply
Posts: 2
Joined: Tue 17 Apr 2007 07:34

Using CommandTimeout makes PostgreSQLDirect .NET stop working

Post by per » Tue 17 Apr 2007 07:52


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?


Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Tue 17 Apr 2007 12:10

What is the version of PostgreSQLDirect .NET you use?
Please send me a small test project to reproduce the problem.
Include definitions of your own database objects and data dump.
Use e-mail address provided in the Readme file.
Do not use third party components.

Post Reply