Re: Command.CommandTimeout bug
Dr. No
I was 100% sure that I had already coded that but when I just looked at the ExecuteReader code, I saw this:
if (connection.driver.Version.isAtLeast(5, 0, 0))
{
TimerCallback timerDelegate = new TimerCallback(TimeoutExpired);
t = new Timer(timerDelegate, this, this.CommandTimeout * 1000,
Timeout.Infinite);
}
This is certainly wrong. I've added a check to make sure CommandTImeout is > 0 before the thread is made.
Subject
Written By
Posted
Re: Command.CommandTimeout bug
October 27, 2006 03:12PM
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.