David Sceppa's Ramblings : MySQL

Recent ADO.NET Entity Framework provider news - Demos and downloads

David Sceppa — Wed, 07 May 2008 08:16:00 GMT

Here are a few quick announcements about ADO.NET providers supporting the Entity Framework. Enjoy!

Core Lab (Connectivity to Multiple Data Stores)

Core Lab was the first ADO.NET provider writer to support Beta 3 of the Entity Framework. Their provider includes connectivity to Oracle, MySQL, PostgreSQL and SQLite databases. For more information, see the announcement on the following pages: http://crlab.com/news/2007/directs430.html and http://crlab.com/news/2008/dcsqlite100.html.

IBM

IBM has released a public beta for their ADO.NET provider that works with Beta 3 of the Entity Framework. For more information, see the announcement on the following page: http://www-128.ibm.com/developerworks/forums/thread.jspa?threadID=203893. IBM also demonstrated their provider in an end-to-end application building scenario using the Entity Framework designer at recent VS Live conference in San Francisco.

MySQL

At the recent MySQL conference in Santa Clara, Reggie Burnett and I co-presented a session talking about MySQL, LINQ and the ADO.NET Entity Framework. As part of the session, we demonstrated using LINQ, Entity SQL and ADO.NET Data Services to access a MySQL database using Beta 3 of the Entity Framework.

Note: Big thanks to Reggie for helping to make this demo work even after injuring his knee. Get well soon.

Npgsql (PostgreSQL connectivity)

Npgsql has released a beta of their PostgreSQL ADO.NET provider that works with Beta 3 of the Entity Framework. You can download the provider at the following page: http://pgfoundry.org/frs/download.php/1730/Npgsql2.0beta3-bin-EntityFrameworkBeta3.zip. For more information on the release, please see the following page: http://pgfoundry.org/forum/forum.php?forum_id=1307.

David Sceppa

ADO.NET Program Manager

The Entity Framework - Not Just For SQL Server!

David Sceppa — Tue, 18 Dec 2007 04:09:00 GMT

As you're hopefully aware, Beta 3 of the ADO.NET Entity Framework is already available. If not, see the ADO.NET team blog here.

You may not be aware of the various ADO.NET provider writers who are publicly pledging their support for the Entity Framework. You can read the entire press release, including information about ADO.NET Data Services (formerly Project Astoria) and ASP.NET 3.5 Extensions here. In terms of third party provider involvement, here are the highlights:

Providers Targeting Publicly Available Versions Within Three Months of RTM

· Core Lab - Providing connectivity to Oracle, MySQL, PostgreSQL and SQLite databases

· IBM - Providing connectivity to both IBM DB2 data server and Informix Dynamic Server (IDS) databases

· MySQL AB - Providing connectivity to MySQL databases

· Npgsql - Providing connectivity to PostgreSQL database versions 7.3+ and 8.x

· OpenLink Software - Providing connectivity to Oracle, Informix, Ingres, Sybase, MySQL, PostgreSQL, DB2, Progress and Microsoft SQL Server databases, and any data source accessible via OpenLink ODBC or JDBC bridge drivers

· Phoenix Software International - Providing connectivity to SQLite databases

· Sybase - Providing connectivity to SQL Anywhere databases

· VistaDB Software - Providing connectivity to VistaDB databases

* - The providers in the list above are also working towards publicly available versions of their providers to work with Beta 3 of the Entity Framework.

Providers Targeting Publicly Available Versions in 2008

· DataDirect Technologies - Providing connectivity to multiple data stores including Oracle, Sybase, Microsoft SQL Server and DB2 via DataDirect Connect® for ADO.NET

· Firebird - Providing connectivity to Firebird databases

If you're writing an ADO.NET provider for the Entity Framework and you're not already in touch with me, please drop me a line at David (dot) Sceppa (at) microsoft (dot) com.

TechEd: Provider Writers Talk About the Entity Framework

David Sceppa — Fri, 15 Jun 2007 21:04:00 GMT

TechEd was a major success. Every time I turned around, more people were asking questions about LINQ and the Entity Framework, though that might have had something to do with the fact that I was standing next to a sign that said "LINQ / Entity Framework".

One of the highlights was the provider writers' chalk talk, which packed the theater area. I'd previously blogged that IBM, DataDirect and Oracle would be in attendance. We also had representatives from Sybase and VistaDB at the talk.

IBM drew the most "oohs" and "aahs" when they demonstrated an early build of their provider working with the 101 LINQ to Entities samples. Each provider writer took some time to talk about their thoughts on customer scenarios, the work they've done so far, etc. The majority of the provider writers talked about how excited they were that both LINQ and Entity SQL allow developers to write provider agnostic queries without having to ask themselves questions like "How do I concatenate strings, construct a join, etc. in my database's query language?"

A few attendees asked about MySQL connectivity. MySQL was unable to attend due to scheduling problems but they are still very much involved. As I mentioned in a previous post, they demonstrated an early build of their provider working with the Entity Framework at the MySQL conference in April.

If you're writing an ADO.NET provider for the Entity Framework and you're not already in touch with me, please drop me a line at David (dot) Sceppa (at) microsoft (dot) com.

ADO.NET at the recent MySQL conference

David Sceppa — Sat, 05 May 2007 01:37:00 GMT

Last week, I attended the MySQL conference in Santa Clara and delivered a presentation on ADO.NET 2.0. It was great to talk to developers building applications targeting MySQL databases via ADO.NET. One developer stayed after my session to comment on how pleased he was to see the changes to the provider model in 2.0 and was even more excited to hear that the Entity Framework would let him focus on writing queries against his model rather than having to think about the query syntax for his back end of choice for string concatenations, etc. Speaking of the Entity Framework, the highlight of the conference for me was attending Reggie Burnett's talk about MySQL and the future of ADO.NET where he demonstrated using an early build of the MySQL provider and the Entity Framework to access MySQL data via both LINQ to Entities and Entity SQL. Here are links to the Reggie's session abstract and to Reggie's blog.