I've been hosting an ASP .NET website (written in Visual Studio, hosted
on Apache with mod_mono on Slackware) for a while now and have been
using ByteFX 0.76 to interface with MySQL. During this time, however,
I've noticed a lot of flakiness with the database connections. A lot of
times funct
On 11/5/05, David P. Donahue <[EMAIL PROTECTED]> wrote:
> Can anyone recommend another one they've used that works well for them?
> I remember when I first started out that it was necessary for me to
> re-compile the data provider myself in order to get it to run in Mono,
> and ByteFX was the onl
By using the official MySql .Net Connector you are making your application GPL, unless you buy a commercial license.
Just a warning :)On 11/5/05, Nimrod A. Abing <[EMAIL PROTECTED]> wrote:
On 11/5/05, David P. Donahue <[EMAIL PROTECTED]> wrote:> Can anyone recommend another one they've used that w
-- Forwarded message --From: Jay Bennie <[EMAIL PROTECTED]>Date: Nov 6, 2005 8:44 AM
Subject: Re: [Mono-list] Recommended MySQL Data Provider?To: Alexandre Miguel Pedro Gomes <[EMAIL PROTECTED]>Alexandre Miguel Pedro Gomes wrote:> By using the official MySql .Net Co
ROTECTED]>Date: Nov 6, 2005 8:44 AM
Subject: Re: [Mono-list] Recommended MySQL Data Provider?To: Alexandre Miguel Pedro Gomes <[EMAIL PROTECTED]
>Alexandre Miguel Pedro Gomes wrote:> By using the official MySql .Net Connector you are making your
> application GPL, unless you buy a
On Sun, Nov 06, 2005 at 01:32:14PM +, Alexandre Miguel Pedro Gomes
scribbled:
> Please take a look at:
> http://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL
>
> It states:
> «*If a library is released under the GPL (not the LGPL), does that mean that
> any program which uses it has to be
I didn't mean to spark so much debate :)
Anyway, now that my development machine is up and running again I'll be
testing the official data provider, since that seems to be the
recommended one.
As for the GPL concerns, I only use the data provider in a very much
seperate data module (web serv
Ok, I just downloaded the source for the MySQL .NET Data Provider 1.0.6,
compiled it (noticed that it had a build named specifically for Mono
1.0, which was pretty cool), and referenced the Mono 1.0 build in my
data module.
But it seems that every function which binds a dataset to a SELECT que
When I converted my project from ByteFx to the newer connector I had to change all the parameter code from @Param to ?Param
Also any param declared as int I had to change to int32
If you get an error in your sql syntax it likely won't bring back a datatable thus the error you see masks the real e
When I converted my project from ByteFx to the newer connector I had to
change all the parameter code from @Param to ?Param
Also any param declared as int I had to change to int32
If you get an error in your sql syntax it likely won't bring back a
datatable thus the error you see masks the rea
I don't understand your example, you are passing the message from the xeception into the constructor for a DataSet?
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.
Joe"David P. Donahue" <[EMAIL PROTE
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.
I
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 fo
. Donahue ; Mono-list@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
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@lists.ximian.com
Sent: Monday, November 07, 2005 4:28 PM
Subject: Re: [Mono-list] Recommended MySQL Dat
ette
To: Bernhard ; David P.
Donahue ; Mono-list@lists.ximian.com
Sent: Monday, November 07, 2005 5:00
PM
Subject: Re: [Mono-list] Recommended
MySQL Data Provider?
Bernard,
Are you willing to share your fix?
I've never had any problems but maybe I'm not g
16 matches
Mail list logo
