Anyone use Devart's MyDirect.NET and/or dbForgeFusion for MySQL?

  • Thread starter Thread starter Cirene
  • Start date Start date
C

Cirene

I am an ASP.NET developer looking to use MySQL as my primary database.

I installed the latest version of the MySQL Connector (5.2). It seems to
work out of the box with Visual Studio 2008. I can create tables, modify
them, add data, create datasets, etc...

Has anyone used Devart's MyDirect.NET and/or dbForgeFusion for MySQL? If
so, what are your thoughts on it? Is it worth the $$$$ or should I just
stick with the FREE MySQL Connector?

(Link: http://www.devart.com/)
 
Cirene said:
I am an ASP.NET developer looking to use MySQL as my primary database.

I installed the latest version of the MySQL Connector (5.2). It seems to
work out of the box with Visual Studio 2008. I can create tables, modify
them, add data, create datasets, etc...
Click to expand...

... and is GPL licensed, or have they changed that lately? The non-GPL
licensed version is kind of expensive, 250+ euro per seat. Don't think
lightly about the GPL license, it does force your own software to be
GPL-ed as well if you distribute it, which means if you transfer it to
another system (e.g. the production server of your client) you've to
open up the sourcecode.
Has anyone used Devart's MyDirect.NET and/or dbForgeFusion for MySQL? If
so, what are your thoughts on it? Is it worth the $$$$ or should I just
stick with the FREE MySQL Connector?

(Link: http://www.devart.com/)
Click to expand...

We use it in our mysql driver/SQL engine in llblgen pro. Core Lab, the
previous name of 'DevArt', isn't really good in doing support but MySql
itself is also a pain in the neck concerning support. mydirect costs
money but way less than MySql's own connector.

Personally I find it rediculous to pay for a connector to a database
system: the db is worthless without the possibility of making a
connection, so why charge for a connector? MySql should release its
provider under teh LGPL, which is the license intended for libraries,
which is exactly what the connector is.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
Cirene said:
So are you more "pro" for the free connector, and more "con" for the
MyDirect.NET stuff?
Click to expand...

No. the 'free' connector isn't free: it's GPL-ed. This means you either
have to open source / GPL your own software OR pay a huge fee to MySql
for every license you need. That's stupid as MySql should be interested
in as much people connecting to their database. Apparently not.

The Corelab connector isn't free, but it's the cheapest around. So
unless you want to GPL your own work, it's the 'best' option around.
'best' is subjective here, as neither connector is really that solid.

FB


--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
I am making a site for a client. So, to make it 'open source' that just
means I have to hand over ALL the source code, in it's entirety, to my
client. Is that correct?
 
Cirene said:
I am making a site for a client. So, to make it 'open source' that just
means I have to hand over ALL the source code, in it's entirety, to my
client. Is that correct?
Click to expand...

The GPL is a distribution license. This means that the license kicks in
when you distribute code which uses GPL-ed code: it in effect limits
your distribution rights of the GPLed code with your software in such a
way that if you don't obey to the license' terms, you can't distribute
nor USE the software.

So if you use a GPLed library in your app A, and you distribute A to
your client, you can only do so if A meets the requirements of the GPL,
as you distribute A and A uses a GPL-ed library. This thus means that
you have to GPL license A. If A is used internally by the client, no
problem unless you don't want to deliver the sourcecode to the client.
If your client uses the software in their software and distribute A with
their app, you do have a problem.

I know, this is a restrictive matter, but that's what the GPL does. So
unless you're tied to MySql, use Postgresql. :) Better database,
provider isn't GPLed (LGPL in fact, so you can distribute as binary) and
less headaches.

FB


--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
Back
Top