mysql

MySQL Changes Mind About Close Sourcing

  • MySQL 6.0's pending backup functionality will be open source,
  • the MyISAM driver for MySQL Backup will be open source, and
  • the encryption and compression backup features will be open source,

where the last item is a change of direction from what we were considering before.

Open Source Springs Up Where You Least Expect It

We had just closed the acquisition of MySQL, so before I wrapped up, I asked, "And would you like a quick update on the newest addition to our family, MySQL?"

The CIO responded categorically with "we don't run MySQL, we run [name withheld to protect the proprietary]." The CISO said, "We can't just let developers download software off the net, you know, we've got regulation and security to worry about." The CTO smiled. Everyone else appeared to be sitting on their hands. I was going to leave it at that. Thanks for the business.

Until a (diplomatically) assertive Sun sales rep piped up, "Um... no, I connected with a buddy of mine over at MySQL, and had him check - you've downloaded MySQL more than 1,300 times in the last twelve months."

After a profoundly awkward silence, one of the individuals from their internal development team piped up, "Actually, everybody uses it. Why bother hassling with license agreements when MySQL's got you covered. We're stoked you bought them."

Things like this, plus all the embedded linux devices out there, mean that open source will be ubiquitous, even if people don't want it to be.

MySQL To Focus Less On Open Source And More On Closed Source

MySQL will start offering some features (specifically ones related to online backups) only in MySQL Enterprise. This represents a substantive change to their development model -- previously they have been developing features in both MySQL Community and MySQL Enterprise. However, with a shift to offering some features only in MySQL Enterprise, this means a shift to development of those features occurring (and thus code being tested) only in MySQL Enterprise.

Also, a clarification on slashdot.

Installing Ruby's MySQL Gem With MySQL Installed Via Fink

If you've installed MySQL via fink and you're going to install the MySQL gem for Ruby and you're getting something like this:

Macintosh:~ brianpuccio$ sudo gem install mysql
Building native extensions.  This could take a while...
ERROR:  Error installing mysql:
	ERROR: Failed to build gem native extension.

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby extconf.rb install mysql -- --with-mysql-dir=/sw/var/mysql/
checking for mysql_query() in -lmysqlclient... no
checking for main() in -lm... yes
checking for mysql_query() in -lmysqlclient... no
checking for main() in -lz... yes
checking for mysql_query() in -lmysqlclient... no
checking for main() in -lsocket... no
checking for mysql_query() in -lmysqlclient... no
checking for main() in -lnsl... no
checking for mysql_query() in -lmysqlclient... no
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers.  Check the mkmf.log file for more
details.  You may need configuration options.

The command you really need is sudo gem install mysql -- --with-mysql-config=/opt/local/lib/mysql5/bin/mysql_config

Virtualization Software

It's articles like this that make me look into buying virtualization software. I'm very not used to having a MAMP stack because managing a LAMP stack, as I have been for years, is worlds easier. Sure Apple has Software Update for the OS and various other software offerings of theres, but how much longer until an all encompassing solution like Debian's (and Ubuntu's) apt software and deb file format?

Syndicate content