By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,992 Members | 1,339 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,992 IT Pros & Developers. It's quick & easy.

which provider should i use?

P: n/a
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.
Nov 20 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a

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 =)

--
____________________
Klaus H. Probst, MVP
http://www.vbbox.com/
"jaYPee" <hi******@yahoo.com> wrote in message
news:gp********************************@4ax.com...
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.

Nov 20 '05 #2

P: n/a
* jaYPee <hi******@yahoo.com> scripsit:
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


Group for ADO.NET questions:

<news://msnews.microsoft.com/microsoft.public.dotnet.framework.adonet>

Web interface:

<http://msdn.microsoft.com/newsgroups/default.asp?url=/newsgroups/loadframes.asp?icp=msdn&slcid=us&newsgroup=microso ft.public.dotnet.framework.adonet>

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>
Nov 20 '05 #3

P: n/a
You could try the MySqlClient from www.sevenobjects.com

It appears to be a free ADO.Net data provider

Regards
jaYPee <hi******@yahoo.com> wrote in message news:<gp********************************@4ax.com>. ..
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.

Nov 20 '05 #4

P: n/a
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

"jaYPee" <hi******@yahoo.com> wrote in message
news:gp********************************@4ax.com...
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.

Nov 20 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.