I was using ByteFx and recently switched to the MySQL Connector.
I think either of these is likely to be more efficient than odbc.
I switched because ByteFX had some problems with certain versions of MySQL.
 
You do have to code things a little different with the new connector compared to ByteFx, see my notes about it here:
http://www.mojoportal.com/BlogView.aspx?pageid=2&ItemID=47&mid=19
 
Hope it helps,
 
Joe


Barbara Plank <[EMAIL PROTECTED]> wrote:
> Yes the latest .NET Connector driver works in Linux running Mono. I'm
> using it in my http://tagcma.com project. If you look at the source, I
> use it quite heavily in the DbLayer/connection.cs.
> http://cvs.sourceforge.net/viewcvs.py/tagelflax/tagml/TAGMLWS/DbLayer/
> conn
> ection.cs?rev=1.110&view=log
>
> You'll find the Mono compile script I use here:
> http://cvs.sourceforge.net/viewcvs.py/tagelflax/tagml/TAGMLWS/CompileW
> ithM
> ono.sh?rev=1.6&view=log

Thanks, I will try .NET connector.

A last question: I read on the mono page that also ODBC is supported,
however, didn't test it. Has anybody experience with it?

In general, which way to access a MySQL database is the right one, suggested
by Mono, or which one is preferable and why?

Ways of accessing MySQL:
- using an ODBC driver
- or a native provider, like ByteFx or rather its successor .NET
Connector/MySQL

(Because I'm using ByteFX and was thinking if there is a better way...)

Thanks,
Barbara


_______________________________________________
Mono-list maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list


joe_audette [at] yahoo dotcom
http://www.joeaudette.com
http://www.mojoportal.com

Reply via email to