Hi Tom, On Thu, Jan 07, 2010 at 04:01:00PM -0500, Tom Hanlon wrote: > Eric, two possible answers to "why", > > 1. > I have developed an allergy to GPL code, and my doctor recommends > that I isolate myself with a BSD licensed bubble. :-)
Since drizzled forked MySQL 6 when it existed, pretty much all code is also GPL (MySQL is, and this is a derived work). There are a few plugins that were written from scratch, and those are suggested to be BSD. Also, libdrizzle was written from scratch and that was also chosen to be BSD. But, the 'drizzle' command line tool is mostly the 'mysql' tool, but using the new libdrizzle instead of libmysql. > 2. > Curiosity.. > I know MySQL really well, and want to learn the differences between > drizzle and mySQL. Yeah. Definitely use 'drizzle' to talk to a drizzle server, but for the time being I'd suggest using 'mysql' to talk to mysql servers (at least until the new 'boots' project is further along). > *note* that I have not even read what license drizzle uses. Just > curious, and I have encountered situations in real life where this > was/is an issue. So reason 1 might be moot. Unless you are talking about embedded databases, the only real concern is the client library license. This is BSD, so no restrictions there. :) > I know the console and the libdrizzle are parts of the same puzzle > and I should move that direction, but there is nothing like a > console interface for educational purposes. So mostly learning and > exploring today. Great! Any feedback is always welcome! -Eric _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
