Bug #28201 Connector/NET fails to throw exception after timeout is reached
Submitted: 2 May 2007 14:21 Modified: 3 May 2007 9:00
Reporter: Randall Carlson Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:5.0.6 OS:Windows (2003 Server)
Assigned to: CPU Architecture:Any
Tags: CommandTimeout

[2 May 2007 14:21] Randall Carlson
Description:
This is a duplicate of Bug #24786.  

My application allows full-text searching on a database of over 2 million email messages.  Each user has the ability to submit a poor search that may cause a long running query to be performed.  I need to be able to trap for a timeout and present a clean error message to the page.

I solely created this report to request action.  Apparently according to the duplicate bug report, a solution has been identified, but it has not been implemented.  Please include this fix in the next release.

How to repeat:
See Bug #24786

Suggested fix:
See Bug #24786
[3 May 2007 9:00] Tonci Grgin
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Explanation: Randall, I am partially to blame for Bug#24786... Please do not submit same report twice, we'll continue discussion there. See my last remarks about upgrading to 5.0.7.