Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by phillup (4419) on 2004.02.11 14:42 (#28333) Homepage Journal
    MySQL's license doesn't says I can't write my own MySQL client library to log these things and distribute it with our product. However, the people at MySQL maintain their license (GPL) prohibits this. Something about the GPL applying to the use of the database and that any access of the database would violate the GPL. Last time I checked, the GPL is a copyright and they can't copyright an idea nor my work -- which leaves them out of luck.

    I think the real issue is the coding of the client library. IANAL, but it seems to me that if it is all clean code... it should be fine... from a legal perspective.
    When you are not distributing any part of the MySQL system, you can use it for free. [mysql.com]

    I know that I write some code w/ Delphi that connects to a MySQL database and have not bought a MySQL license. But, I don't know if Borland paid to have that ability.

    I don't distribut the database, it is up to the client to get and set up their database and take care of any licensing issues.

    My limited understanding of the GPL was that it could not limit how a product is used and that MySQL.com is, in this case (if the claims are true) trying to tie the licensing to how it is used. While they can certainly control distribution of the mysql code, when included with commercial software... I don't think (remember... IANAL) that they can control how the software is used in conjunction with a totally separate piece of commercial software.