MySQL connector?

[rockdale]

Hi, All

This is the first time that I code asp.net against mySQL database. I am
confused that which connector should I use 'cause I do not want make
the wrong choice and have some problems later on?

one is from mySQL official website

http://www.mysql.com/products/connector/net/

or ODBC/OleDB driver that comes with MS .Net?


Any experience can share with?

Thanks a lot
-rockdale

 

[John Timney \(MVP\)]

I would try the mySQL one first. Its much more likely to be optomized for
the DB and you'll get good supprot from the mySQL community. Also, if I
recall www.asp.net has a section dedicated to it.

Regards

John Timney (MVP)

 

[Bren]

Hi Rockdale

I use the MySQL one in .NET 1.1 and .NET 2. I have also used the
SqlDataSource control which comes as part of VS 2005 and added the
connection string into web.config.
From that you can then reference the connection string and programmatically
assign your SQL statement in your code behind page.
I wouldn't advise using the "configure datasource" wizard with the
SqlDataSource as the code that VS2005 creates MySQL sometimes complains
about.

Regards
Bren

 

[Mark Rae]

Any experience can share with?

Hmm - I've done a fair bit of work with mySQL v4 and v5, but have only used
the native .NET data provider from CoreLab (http://www.crlab.com/mysqlnet/).
However, I know people who use the one supplied by mySQL themselves
(http://dev.mysql.com/downloads/connector/net/1.0.html) and who recommend it
highly.

Is there any reason that you would use OleDb or (even worse!) ODBC instead
of a native .NET data provider...?

 

[rockdale]

Thanks for those prompt replies.

All my previous experience are asp.net against MS SQL.
I am still using Visual Studio 2003 and given that I have the data
access black (from microsoft) implemented. I was wondering if I use the
ODBC/OleDB connector, then I do not need change too much code,
theoritically it should be transparent to the database, right?
Other I need rewrite my wrapper for MySQL connector.

If the MySQL.Net is highly recommended, then it worth to rewrite the
data access block to use MySQLClient...

thanks
-rockdale

 

[Mark Rae]

If the MySQL.Net is highly recommended, then it worth to rewrite the
data access block to use MySQLClient...

Yes absolutely! See here:
http://dev.mysql.com/tech-resources/articles/dotnet/index.html, and scroll
all the way to the bottom, noting specifically "Performance is a big
negative factor for ODBC as it involves too many layers."

ODBC is a good 10 years old now, and technology has progressed. The native
..NET provider will give you by far the best performance.