Bug #15038 Setting CommandTimeOut does return set value
Submitted: 17 Nov 2005 23:55 Modified: 26 Dec 2005 8:34
Reporter: Darren Hill Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / NET Severity:S3 (Non-critical)
Version:1.0.6 OS:Windows (Windows XP)
Assigned to: Assigned Account CPU Architecture:Any

[17 Nov 2005 23:55] Darren Hill 
Description:
When setting the MySqlCommand.CommandTimeOut, checking the value immediately afterward does not return the same value that was set previously.

How to repeat:
MySqlCommand cmd = new MySqlCommand();
cmd.CommandTimeout = 60;
if( cmd.CommandTimeout.Equals(60) ){
     //Success!
}
else{
    //Failed!
}
[18 Nov 2005 0:53] Darren Hill 
My mistake, the issue is that setting the CommandTimeout is actually not supported.  Any reason for this?
[26 Nov 2005 8:34] Vasily Kishkin 
Why did you write CommandTimeout is not supported ? Where can I read it ?
[27 Dec 2005 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".