Re: Command.CommandTimeout bug

[Reggie Burnett]

I've updated the documentation.

> 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.
Can you show me how you think this? I don't see where this is the case.

>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.
The value gets multipled by 1000 in the code because that part of the code needs the timeout in milliseconds, not seconds. The max value of CommandTimeout is indeed Int32.MaxValue.