which provider should i use?

  • Thread starter Thread starter Klaus H. Probst
  • Start date Start date
K

Klaus H. Probst

I haven't tried to hit MySQL from .NET, but at least the OLEDB->ODBC bridge
from VB6 and C++ worked fine, so talking to it through the ODBC provider in
..NET should be your best bet, at least until the managed provider is a bit
more mature. But ultimately you use the one with fewer bugs =)
 
I am new to mysql and wondering which one is the best for accessing
mysql. I have read this article from mysql website:

At present, one can access MySQL using the following 3 interfaces
supported by MySQL.

The ODBC.NET Solution - MyODBC Driver.
Using MySQL Native .NET Providers.
Using the OLEDB.NET Solution - MyOLDDB Provider

any ideas is greatly appreciated.
 
jaYPee,
I would choose the provider in this order, unless one of the three proved to
be significantly faster then the others:

First choice: Using MySQL Native .NET Providers.
Second choice: Using the OLEDB.NET Solution - MyOLDDB Provider
Third choice: The ODBC.NET Solution - MyODBC Driver.

Native providers should be fastest as you are (hopefully) avoiding interop.
OLE DB is newer then ODBC so I would pick that next. However I have seen
cases where ODBC is faster then OLE DB for relational data, so I would test
the speed of all three to see which performs the best.

Hope this helps
Jay
 
Back
Top