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

use Perl Log In

Log In

[ Create a new account ]

shiflett (3841)

shiflett
  (email not shown publicly)
http://shiflett.org/

I own a small PHP consultancy located in New York. I just finished writing my first book for O'Reilly, entitled Essential PHP Security. Yes, I'm a PHP guy hanging out on a Perl site.

Journal of shiflett (3841)

Wednesday February 11, 2004
03:26 AM

MySQL Licensing

[ #17350 ]

It's been a week since he wrote this (I've been busy with PHPCommunity.org), but Theo has written a nice testimonial about the problems developers are facing with MySQL's licensing.

Zak has been hosting an open license review recently. Hopefully good things will happen as a result. I encourage everyone to voice any concerns you have; MySQL AB seems very willing to listen and to try to resolve and/or clarify any legitimate concerns.


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

MySQL Licensing 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • 404 Not Found (Score:2, Informative)

    by bart (450)
    That link points nowhere... A little search on Google for "theo schlossnagle MySQL" brought up this page [schlossnagle.org] (archive [omniti.com])... is this what you were aiming at?

  • That will teach me to post at 3 AM. :-)

    It's now fixed. Thanks.

  • 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, b
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.