[Mono-list] Recommended MySQL Data Provider?

[Joe Audette]

Bernard,
 
Are you willing to share your fix?
I've never had any problems but maybe I'm not getting a high load scenario.
 
Thanks,
 
Joe

Bernhard <schwimmlehrer at gmail.com> wrote:
1.0.4 had a very serious bug. Under high load the connecting/timeout code eats all threads in the tread pool. I am using a version 1.0.4 that I fixed myself and did not yet update to the newest version.
 
HTH
Bernhard
----- Original Message ----- 
From: Joe Audette 
To: David P. Donahue ; Mono-list at lists.ximian.com 
Sent: Monday, November 07, 2005 4:28 PM
Subject: Re: [Mono-list] Recommended MySQL Data Provider?


You may be having some problems due to the newer versions of the connector not working 100% in mono. version 1.05 of the connector was completely broken for mono, they fixed some stuff in the newest one but I think the 1.04 was a good one. In any case the one I'm using is older and it works good for me. You can download it from my site at http://www.mojoportal.com/download
get the data layer for MySQL and the MySql.Data.dll is contained inside the zip. Drop that in your bin instead of the one you are currently using and it may help. If your current one is in the GAC you may need to remove it because it will be used in preference to one in the bin. The version in my zip file is not signed with a strong name key so you won't be able to put it in the gac. Alternatively you could download the src for my project which includes the source for the MySql connector version I'm using. I compile it in VS and it works fine deployed on mono.
 
hope it helps.
 
Joe

"David P. Donahue" <ddonahue at ccs.neu.edu> wrote:
> I don't understand your example, you are passing the message from the 
> xeception into the constructor for a DataSet?

The idea was to always return a dataset, even an empty one (in which 
case the title of the dataset would be the error message). I guess it 
doesn't work as well as I'd hoped.

> If you want to know the real error I would remove the try catch 
> entirely. Its generally not recommended to catch the most generic error 
> anyway.

Well, that did show a new error:

"Keywork not supported.
Parameter name: direct"

It hadn't even occurred to me that I would need to change my connection 
string, which is the only place in my code that has the word "direct." 
I just tried a really simple one:

"Server=sername;Database=dbname;Uid=username;Pwd=password;"

But now all functions result in a "Thread was being aborted" error.


Regards,
David P. Donahue
ddonahue at ccs.neu.edu
http://www.cyber0ne.com
_______________________________________________
Mono-list maillist - Mono-list at lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list


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

---------------------------------


_______________________________________________
Mono-list maillist  -  Mono-list at lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list


joe_audette [at] yahoo dotcom
http://www.joeaudette.com
http://www.mojoportal.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-list/attachments/20051107/987f97de/attachment.html