Page 1 of 1
What's the deal with the MySQL GPL licence?
Posted: Wed Jul 07, 2004 10:13 am
by tomfra
I've read something about the MySQL interpretation of the GPL licence and I am not sure I understand it.
If I create a proprietary script in php which uses MySQL database for storing and retrieving data (like most php scripts do), do I have to release this php code under GPL or buy their commercial licence?
Thanks!
Tomas
Posted: Wed Jul 07, 2004 12:04 pm
by feyd
It's best to ask a lawyer about it.. the GPL has several gray areas..
Posted: Wed Jul 07, 2004 12:47 pm
by tomfra
I think I do know how the GPL licence works, it's the way MySQL AB interprets it that makes me worried. I know it would be best to ask a lawyer who specializes on this area but because this topic does affect so many members of this dboard I believe someone here has to know more about it.
Tomas
Posted: Wed Jul 07, 2004 12:49 pm
by feyd
Have you tried asking them?
Posted: Wed Jul 07, 2004 12:54 pm
by tomfra
No, I haven't. I will but I would first like to know more from someone not associated with MySQL AB. Independent & unbiased opinion is what I want most.
Tomas
Posted: Wed Jul 07, 2004 2:00 pm
by Weirdan
for the first, GPL FAQ stated:
GPL FAQ wrote:
......
However, when the interpreter is extended to provide "bindings" to other facilities (often, but not necessarily, libraries), the interpreted program is effectively linked to the facilities it uses through these bindings. So if these facilities are released under the GPL, the interpreted program that uses them must be released in a GPL-compatible way. The JNI or Java Native Interface is an example of such a facility; libraries that are accessed in this way are linked dynamically with the Java programs that call them.
......
but MySQL has made an exception for software released under PHP license:
MySQL licensing FAQ wrote:
Because PHP and MySQL use different incompatible open source licenses, we have created a special exception to encourage and promote the use of MySQL in the PHP community. MySQL AB gives permission to distribute derivative works that are formed with GPL-licensed MySQL software and with software licensed under version 3.0 of the PHP license. You must obey the GNU General Public License in all respects for all of the code used other than code licensed under version 3.0 of the PHP license.
but that's not the case because you're not going to release the program under PHP license, are you?
Thus you have to purchase the commercial MySQL license to be able to use MySQL client library calls in your proprietary PHP application.
Do not consider this as legal advise, it's just my 0.02$.
Posted: Wed Jul 07, 2004 8:52 pm
by tomfra
And what about if I create a script in php that uses MySQL database, sell the php script to a customer who installs it on their webhosts who has a MySQL server installed. What about the customer? Would they be allowed to use proprietary php scripts that needs MySQL to work if there is no commercial licence installed on that server?
Or I could probably create 2 php files instead of one and include all of the MySQL calls in one of them which would be distributed under the php or GPL licence and all of the other code in another file which would be proprietary. Probably. But that would be a nuisance I could really live without.
Tomas
Posted: Thu Jul 08, 2004 10:21 am
by tomfra
It looks like there is nothing to worry about after all
From the information I found at
http://php.net/manual/en/faq.databases. ... mysql.php5 it seems that the current versions of PHP are using the old LGPL version of MySQL client libraries and they will not be including any MySQL client libraries in PHP 5.
Tomas