Bug #56806 | Default Command Timeout has no effect in connection string | ||
---|---|---|---|
Submitted: | 15 Sep 2010 19:32 | Modified: | 13 Oct 2010 9:22 |
Reporter: | Aren Cambre | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S2 (Serious) |
Version: | 6.3.4 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | entity framework |
[15 Sep 2010 19:32]
Aren Cambre
[7 Oct 2010 21:13]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/120306 840 Reggie Burnett 2010-10-07 - fixed MySqlCommand.Clone so that the default command timeoout functionality is not disabled when you clone a command (bug #56806) The problem was that MySqlCommand.CommandTimeout has a hidden function. If the underlying value is 0 then the default value is returned, otherwise the underlying value is returned. In our Clone method we were using CommandTimeout which would return the default value rather than the underlying value. This would, in effect, disable our default command timeout which relied on the underlying value still being 0.
[7 Oct 2010 21:16]
Reggie Burnett
fixed in 6.0.8, 6.1.6, 6.2.5, 6.3.5+
[11 Oct 2010 18:29]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/120528 843 Reggie Burnett 2010-10-11 incorporating new default command timeout handling into my clone patch (bug #56806)
[13 Oct 2010 9:22]
Tony Bedford
An entry has been added to the 6.0.8, 6.1.6, 6.2.5, and 6.3.5 changelogs: Setting the Default Command Timeout connection string option had no effect.