In your release notes you wrote "Only when these Async API's are run on an RDBMS provider with native async support (i.e. .NET 4.5 SqlServer or MySql) will you benefit from true non-blocking Async I/O, otherwise it fallsback to pseudo async support, i.e. synchronous I/O datasets wrapped in Task Results.".....

But does the latest MySQL Connector really support true non-blocking I/O? When I look at the implementation, they just wrap a Task around ExecuteDataReader/ExecuteNonQuery.

This is a must

yep great idea

I agree - async makes a lot of sense!

with no async support for OrmLite, it becomes difficult to consider Service Stack for ORM, and we have to go back to use regular ADO.net or have Entity Framework

I agree - Please provide async support.

I agree. We are considering making a purchase, but are sadden by the fact that our IIS threads will be IO bound if we use ormlite. We love the performance and need the load support. We don't want to have to go back to EntityFramework just because it has async support.

I mean provide async support not provider...