Bug #40287 BeginExecuteReader missing overload that takes a callback and user-state
Submitted: 23 Oct 2008 19:00 Modified: 11 Nov 2008 16:47
Reporter: Bassam Tabbara Email Updates:
Status: Closed Impact on me:
Category:Connector / NET Severity:S4 (Feature request)
Version:5.2.3 OS:Any
Assigned to: CPU Architecture:Any

[23 Oct 2008 19:00] Bassam Tabbara
MySqlCommand.BeginExecuteReader does not currently have an overload that takes a AsyncCallback and object user-state. This is not consistent with the Asynchronous Programming Model guidelines in .NET and also not consistent with MySqlCommand.BeginExecuteNonQuery.

It also make this method less useful in truly async scenarios such as ours.

How to repeat:
None needed.

Suggested fix:
Add an overload that takes a AsyncCallback and object user-state.
[24 Oct 2008 15:10] Tonci Grgin
Hello Bassam and thanks for your report.

I do agree with you but this is actually a feature request, no matter how it affects you or your code. Could you please lower the severity so I can verify it?

Also, I have already brought this problem before c/NET team leader.
[24 Oct 2008 16:25] Bassam Tabbara
Lowered Severity per request.
[24 Oct 2008 16:35] Tonci Grgin
Thanks for your reasonable feature request Bassam. We should be hearing from Reggie regarding this problem soon.

Verified just like described by looking into latest sources.
[11 Nov 2008 16:47] Reggie Burnett
Created worklog to implement this.  Should be implemented either in 6.0 or 6.1
[6 May 2009 0:01] Thiago Sayao
I need this, please!
I can't make my web site scale with async responses if mysql doesn't support it.