There was once a big hooplah about the MySQL Storage Engine Architecture and how it was easy to just slot in some other method of storage instead of the provided ones. Over the years I’ve repeatedly mentioned how this wasn’t really …

Berkeley DB (BDB) is undoubtedly the workhorse among the opensource embedded database engines. It started as a university project in the mid-eighties and was further developed by Sleepycat Software, until it got acquired by Oracle in February 2006.

I had the impression that BDB had lost a lot of its popularity among opensource developers to SQLite in recent times, which has evolved into becoming the default choice for developers looking for an embedded data store. I'd assume primarily because the code is not released under any particular license, but put in the public domain …

In a nutshell: What’s New in MySQL 5.1.

Release notes: Changes in release 5.1.x (Production).

And yes, very early on (at about two minutes in), I talk about my take on Monty’s controversial post at Oops, we did it again.

To play the video directly, go to http://technocation.org/node/663/play. To download the 146 Mb video to your computer for offline playback, go to http://technocation.org/node/663/download. The slides …

April 1st is still more than a month away and at least one rumour about Oracle’s upcoming purchases is true: today the software giant annnounced their acquisition of Sleepycat Software, the makers of Berkeley DB (and various other products).

One interesting point is that Berkeley DB was already seeing competition from SQLite (which is an excellent, fast and free (as in beer and freedom) RDBMS). I wonder how much the acquisition is going to drive adoption of SQLite?

Additionally, Oracle now owns both half of MySQL’s transactional storage engines, which perhaps gains them another measure of control over the Swedish upstart. (The other engines are …

Do note: This is my personal blog, and all thoughts expressed here are my own, and are not necessarily shared by my employer.

So... I was talking with my cohort, Ulf about the future of MySQL and MaxDB.

He got me thinking about what the relationship between MySQL and SAP/MaxDB really is. What does the "partnership" mean a few levels below the VP?

To me, it means that, going forward, I expect to see a lot of communication and camaraderie between the MySQL and MaxDB developers. I expect to see a lot of MaxDB's rock solid, tried and true code become shared libraries which are then linked against by MySQL. I expect to see a lot of MySQL's tools that provide the usability and simplicity that the community has come to expect from them generalized in such a way that they can be used to administer a MaxDB system. I expect to see MaxDB adopt …