Standish Group says open source costs vendors $60 billion. OpenLogic launches Open Source Census. Novell annnounces SUSE Appliance program. (and more)

“Free Open Source Software Is Costing Vendors $60 Billion,” New Standish Group International Study Finds, The Standish Group International (Press Release)

Global Open Source Census Launches to Count Enterprise Use of Open Source Software, OpenLogic (Press Release)

Novell Announces SUSE Appliance Program, Novell (Press Release)

Sun Microsystems Introduces MySQL Workbench, Sun Microsystems (Press Release) …

At least with any luck it will be.

For those of you unaware, I recently left AdBrite, so I had some fears that the open source release of my tools might not happen. I was reassured today, however, that things are moving forward so that raises my hopes considerably.

Also, if you are looking for someone to help your organization with all areas involving scale (and not just MySQL), visit my LinkedIn public profile for detailed information about me and what I've done in the past.

MySQL has a storage engine slash table type of "memory" or "heap". The memory engine keeps the table in memory instead of on a disk. It can be very fast. It has a couple of problems. One problem is that it handles varchar types poorly and wastefully.

This was a problem for eBay. So they paid one of their own smart employees to fix that problem.

Other people have heard about that patch, and asked for it. I couldn't give it to them, and it all started bogging down in pointless legal discussions. At least by the lawyer people and people who are into lawyer people.

So the author of the patch took a sword to the knot, and released the patch to the public.

Here it is: http://code.google.com/p/mysql-heap-dynamic-rows/



This project provides support for variable size records (aka …

Here’s a rundown of Thursday (day 3) of the MySQL Conference and Expo. This day’s sessions were much more interesting to me than Wednesday’s, and in fact I wanted to go to several of them in a single time slot a couple of times. Inside the PBXT Storage Engine This session was, as it sounds, a look at the internals of PBXT, a transactional storage engine for MySQL that has some interesting design techniques.

Keith Murphy and his hard-working crew have released the spring 2008 issue of MySQL Magazine. Go take a look – it includes quite a few articles on various topics, even a mention of our upcoming book (High Performance MySQL, Second Edition).

MySQL has a lot of string data types - CHAR, VARCHAR, BLOB, TEXT, ENUM and bunch of variants such as VARBINARY but I think it is not enough

I would also like to see type HEXCHAR which would be able to store hex strings, such as those returned as MD5() and SHA1() efficiently. With little modification it could work for UUID() as well (it adds some dashes). Currently it is quite inconvenient to deal with strings like that in MySQL. Either you store them as strings and waste space or you spend them as binary and deal with inconvenience of having not readable strings in the table OR adding UNHEX() everywhere - which also adds overhead.

Another one I would like to see is zBLOB or zTEXT (or call them BLOB COMPRESSED/ …

I’ve hacked around a bit to get PBXT to compile in tree, and pulled in the Maria engine. Both are latest source.

So, want to try out Maria?

Want to try out PBXT?

Just want to do ./configure and go with it, just like building a normal MySQL Server?

Grab the -stew tree. Source tarball here:

mysql-5.1.24-stew1.tar.gz

(it’s based on something close to 5.1.24… and I’m going to switch some of my systems over to it rather soon… already done some good benchmarks on one of my apps).

feedback much appreciated.

UPDATE: Got x86-64 Linux. Try my binary tarball (built from above src tarball). Built on Ubuntu Gutsy (my laptop). So it may (or may not) work. …

Is proprietary software really that bad? Or is it a fair contract between consulting corporations? The answer is "It depends" and "Not really." Both depend on the strictures a vendor puts in place to inhibit its ability to lock a customer into its software. In MySQL's case, MySQL has no intention to lock customers in, as far as I can tell. It just wants to convince customers to pay so that it can prove its worth.

MySQL is contemplating introducing extensions to its core database that are only available to paid subscribers, for compelling reasons. This is not, as has been suggested, in and of itself proprietary. Red Hat does the same by providing an initial gate to its RHEL code which only a paid subscriber can access unless they get it from an existing customer of Red …

Just as a note the Ebay memory engine has been released:
http://code.google.com/p/mysql-heap-dynamic-rows/

This is awesome to see open sourced. It is an extension to the current Memory engine that has the engine using less memory (aka it really implements variable size character types).