MySQL Bugs: #77198: C# async method does not work

Bug #77198	C# async method does not work
Submitted:	30 May 2015 23:49	Modified:	1 Jun 2015 6:35
Reporter:	Danny Chu	Email Updates:
Status:	Verified	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	6.9.6	OS:	Microsoft Windows
Assigned to:		CPU Architecture:	Any
Tags:	async

Description:
Hi, it seems like the async methods does not work at all. It runs synchronously.

I made a thread here on Stackoverflow where i explained it:
http://stackoverflow.com/questions/30551459/mysql-c-sharp-async-methods-doesnt-work/305515...

How to repeat:
I wrote the examples in stackoverflow.

http://stackoverflow.com/questions/30551459/mysql-c-sharp-async-methods-doesnt-work/305515...

Hello Danny Chu,

Thank you for the bug report.
Verified this behavior on Visual Studio 2013 (C#.Net) with  MySQL Connector/Net 6.9.6.

Thanks,
Chiranjeevi.

screenshot

Attachment: 77198.PNG (image/png, text), 34.95 KiB.

Hi there,

We would love to use fully asynchronous methods, but can't until the methods are async all the way down, that is, until the IO boundary.

Is this going to be fixed sometime soon?

The discussion here suggests the development team don't understand the meaning of supporting real async methods or don't care about it: http://bugs.mysql.com/bug.php?id=70111

Could someone from the development team give some position on when or if this will be implemented at all? Can someone contribute this to the driver?

This should be priority 1. MySql is the only driver for .net that doesn't support this yet.

Lowing the priority due we do not have plans to add or change any functionality or implementation on the async support. We will be working on having better functionality that supports new capabilities for .NET applications like .NET Core Version.

This is a shame, since Gabriela obviously didn't understand what this means.

In short, the team lied about implementing this, some developer lied about finishing this task, nothing works as expected and they're just moving on.

Way to go.

It's a shame the team don't seem understand what an absolute deal-breaker this feature is for using MySQL at all.