Peter Bradley wrote:
Please contact MySQL at:
http://www.mysql.com/company/contact/?topic=licensing
before assuming that using connector/net means that your software has
to be GPL
err... it's very simple:
if you reference/link/use a GPL-ed piece of code in your own code, your
code HAS TO BE licensed under the GPL as well. Read the GPL, it's very
simple.
You can get away by not doing that IF you don't distribute your
application. However, as soon as you distribute your application to
whatever (that is: even another machine!), you ARE violating the
license.
Please note that if you are using MySQL in a "commercial product"
then you need a commercial license anyway.
I don't know the MySql license through and through, but the GPL is
pretty clear: if you create a commercial application, you can still use
the GPL-ed software, as long as you GPL your own software as well.
However I think that they mean if you are distributing your product,
rather than using it in-house. If you are just developing an
in-house system using MySQL and connector/.net I don't think you need
a commercial license or to publish your code.
With licensing issues, 'I think' is not enough. You have to be sure.
GPL is a distribution license, as many others.
This means that if developer A writes a piece of code and uses a
GPL-ed ADO.NET provider, and the software is never distributed by A to
whatever other system (that also includes a co-workers box, that's also
distribution), then A doesn't have to GPL his software. As soon as A
does distribute the code, he will have to license his own code as GPL,
that's the license he has to obey to to be able to USE the gpl-ed
ado.net provider.
If you are producing an in-house product and you are not distributing
it, the GPL places no burden on you whatsoever (i.e. you do not have
to make your code available). The GPL only insists you make your
source code available if you distribute your product (which to most
of us mean, "Sell it" in all practical terms) - and if this were the
case, you'd need a commercial license for MySQL anyway.
in-house distribution is also distribution. Distribution from your
laptop to the server of your customer who uses it in-house is also
distribtion.
Please check this with MySQL. Unless one of MySQL AB's lawyers is
posting here, none of us is qualified to give you an answer vis-a-vis
licensing of MySQL or connector/.net
I can tell you, Mysql's lawyers are very keen on this. So stay on the
safe side: either use a commercial provider or use another database.
FB
>
HTH
Peter
"Frans Bouma [C# MVP]" <pe************ ******@xs4all.n lwrote in
message news:xn******** *******@news.mi crosoft.com...
Frank Rizzo wrote:
I've been given a project to work with which involves connecting
to MySQL from .NET 2.0 app. I've googled looked and there is a
metric ton of different MySQL ADO.NET providers from different
people.
>
Is there a consensus on which one is the most stable, more or less
supported and has good support for the standard MySQL features
(e.g. stored procs)?
MySql's own: it's GPL-ed (free) though you then also have to GPL
your own software. OR you have to pay 250$+ per developer for a
commercial license.
Core Lab's: it's commercial, but very inexpensive. They had their
problems in the past but it works fairly well.
Unless you're willing to making your own code GPL licensed, i'd go
for core lab's.
--
------------------------------------------------------------------------
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#)
------------------------------------------------------------------------
