Thankfully, I found one very good post with a clearly rounded whole question and solid answer from someone at MySQL AB:
http://forums.mysql.com/read.php?4,30183,45753#msg...
In Summary:
Question: "Our plan is create an application that will just connect to MySQL Server running on a different machine using Database Connections like MyODBC 3.5 [... do I need] to buy a License from you (MySQL AB) for using MySQL Server?"
Answer: "A good option for you may be becoming a MySQL Certified partner, at the basic level this is just USD 595/yr. See [solutions.mysql.com] for details.
Under the partnership, you can get an optional (but free) non-GPL license for any of the MySQL client libraries, for distribution linked with your closed source product."
Case closed.
-Matt
Comments (4)
Nonsense. They didn't answer the question -- they stated what would one option be, of course stating one that would benefit them.
Posted by Berislav Lopac | September 18, 2006 4:25 PM
Posted on September 18, 2006 16:25
Alright, then... you call MySQL AB and ask, then post it here.
-Matt
Posted by MattL | September 18, 2006 7:28 PM
Posted on September 18, 2006 19:28
I'm not sure what is so confusing here. The client libraries (MySQL ODBC/.NET/JDBC) are all released under the GPL (not the LGPL). That means if you distribute the connectors in or with your code, your own license will need to be compatible with the GPL.
As for the other option, you can probably purchase a commercial license of these connectors (or MySQL Network) and get a commercial license. But that option isn't any cheaper.
More info on the MySQL interpretation of the GPL and their commercial license is available at:
http://www.mysql.com/company/legal/licensing/commercial-license.html
Note how broad their definition of "distribution" is.
PS Nice blog you have here Matt. ;)
Posted by Doug Luxem | September 19, 2006 9:34 AM
Posted on September 19, 2006 09:34
Thanks, Doug -- Good to see you around!
-Matt
Posted by MattL | September 20, 2006 8:18 AM
Posted on September 20, 2006 08:18