MySQL Bugs: #40832: .net Connector 5.2.3 Sets Pooling=false When MySqlCommand.Cancel() is Called

Bug #40832	.net Connector 5.2.3 Sets Pooling=false When MySqlCommand.Cancel() is Called
Submitted:	18 Nov 2008 17:53	Modified:	19 Nov 2008 9:54
Reporter:	Galen Guilbert	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	5.2.3	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	.net Connector 5.2.3 Pooling

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
I see in the source where connection pooling is turned off if MySqlCommand.Cancel() is called.  This is typically called when trying to kill a query, but I don't understand why pooling gets set to false.

How to repeat:
Create a connection with pooling turned on.  Timeout a stored procedure, then inspect the Settings property of a subsequent connection object.

Suggested fix:
Don't turn off pooling based on a cancel.

Hi Galen and thanks for your report.

I believe it's duplicate of Bug#40091 which is fixed in c/NET 5.2.4. Please download new driver from http://dev.mysql.com/downloads/connector/net/5.2.html and inform me of result.