MySQL Lifecycle Policy Calendar

The official MySQL Lifecycle Policy calendar terminates the end of the Active Support Lifecycle for MySQL 4.1 at the end of this year. The product is then entering the Extended Support Lifecycle. Please click on the image and read "What is the difference between Active Lifecycle and Extended Lifecycle support?" to understand the implications of this.

Have an Intel Mac? Rely on SIP soft phones, like X-Lite? Realize that it always crashes?

Try the beta, from CounterPath. It’s not called X-Lite, its beta, so it might eat your babies, but I’ve been using it for a while (because MySQL loves VoIP), and it works a charm. Looks like my office phone is back in business, even when I’m on OS X.

This happened a few days ago a few houses up our street: Man crashes car into swimming pool (in the Australian, other mentions on ABC and news.com.au).
(There's a Dutch driving instruction joke: "kaboom = halt!, splash = water". This nutball managed to do both at the same time.)
FYI: two kids had just come out that pool only minutes before. The parked car (with a baby seat) had noone in it at the time. Its smashing into a pole caused a powerline across the road to snap, cutting the power to two houses and putting a rather dangerous live wire on the road, near debris, sparks and water).

A few years ago something similar happened early one …

One annoying aspect of SQL is that sometimes you really want to get some result out of an INSERT or UPDATE statement. But in MySQL, you can. It's just a nifty construct.

First just an UPDATE:

UPDATE tbl SET col = (@var := col), bla=value WHERE ...
SELECT @var

So, you can assign a column to itself (MySQL does a read before write, for updates), but also assign that value to a server-side variable which you can then retrieve. That's how you get data out of a row you're updating!

Now, how about the case where you need to insert something into one table, but regardless of whether or not it already existed you need to insert or update info into a second table (and also the id from the first table).
That's your christmas challenge from me.... no selects or transactions necessary. Good luck!

Need to post more regularly... once I have posting from the plam sorted out.
Actually, just posting more regularly would be a big plus.
(Sounds like a good new year's resolution)

Plugins... Nearing completion. Yay! Quite a reasonably tidy server variables declarations and implementation now. Just one variable which I may eliminate and free (potentially a few kilobytes) as it is no longer strictly necessary.
Right now, only InnoDB has been modified to take advantage of it - easily make MyISAM make use of it for it's few variables.
Need to concider splitting out more subsystems so that more globals can be removed.

Solid Information Technology, best known to the open source community as the providers of a new enterprise storage engine for MySQL, announced this week that it secured four million euros for the expansion of its open source initiatives (press release). The investors participating in this financing were Apax Partners and CapMan.

Although Solid is based in the United States, its investors are both European. I guess this explains why the press release lists the funding amount in euros and not dollars. I wonder if we will see more funding announcements preferring the euro as the currency of record. I left the euro symbol out of this post due to some character set issues.

As 2006 nears its close, Dave and I decided to try to do a "Year in Review" sort of post or two. You can find Dave's here.

This has been an exceptional year for open source (and for me, personally, though Arsenal didn't contribute much to that). I was with Alfresco all year, as well as the advisory boards for SugarCRM, JasperSoft, Specifix, MuleSource (sort of - still waiting for my paperwork, Dave :-), Intoto, and Bungee Labs, as well as the board of OSI and the Open Source Business Conference. These gave me a bird's eye view into different sectors of the industry, so as to separate hype from reality in open source.

Guess what? All signs are positive for open source, no …

Welcome to the 24th edition of Log Buffer, the weekly review of the database blogosphere. To begin, some news about that other open source RDMBS, Firebird. Foremost is an item on Firebird News pointing to the Firebird development roadmap for 2007. On the same site, a link to a summary on Wikibooks of SQL dialect differences [...]

MySQL has today refined its licensing scheme from “GPLv2 or later” to “GPLv2 only“, in order to make it an option, not an obligation for the company to move to GPLv3.

Specifically, this means that copyright notice in the MySQL source code files will change from referring to “either version 2 of the License, or (at your option) any later version” to “version 2” only, in the MySQL 5.0 and MySQL 5.1 code bases.

Six years ago in the summer of 2000, when MySQL AB licensed its software under the GPL, our founders David Axmark and Michael Widenius made this choice because the GPL was a license followed and respected by everyone. We have kept to it, because the GPL is the most palatable license, and poses the least friction for our user base.

MySQL has been part of the GPLv3 Committee …