Command.CommandTimeout bug
Posted by:
Dr. No
Date: October 23, 2006 08:51AM
Hi,
I believe I found a bug in the Command object. The Documentation says that the default value of this parameter is 0. I would expect that 0 means an infinite time. However it seems that Commands that result in an ExecuteReader call do really get a timeout of 0s which means that almost no database call succeeds. This should be corrected I guess.
Furthermore I found out that the default value is actually not 0 as indicated in the documentation. Looking at the source files I see that it is 30, not 0. Either the documentation or the implementation should be corrected I guess.
Finally when one sets the CommandTimeout property to Int32.MaxValue, then this will not work. The maximum value for the timeout is Int32.MaxValue / 1000 becuase the value gets multiplied by 1000 at some point during the execution. This should be mentioned in the documentation if possible.
Dr.No
Subject
Written By
Posted
Command.CommandTimeout bug
October 23, 2006 08:51AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.