Ok, seems like this is one of my yearly rituals: Trying to build some momentum behind PDO. So far it has remained lingering after every such attempt, not that this isn't partially at least my fault. I think last time I said I would work on the tests and in the end I didn't get anywhere. Unfortunately nobody came around to kick me for this lack of commitment and so the idea faded again. So enough with the gloom today is a fresh start and I think one thing has changed significantly since then: We have people posting patches for PDO on internals and someone (aka Matteo) that has been fairly steadily trying to close some tickets. Pierre also seems to be interested in putting in some time. Scott has always been committed to the SQLite driver and Ilia and …

So I guess the argument that Monty is putting forth is that MySQL's future depends on some company exploiting their ownership of the MySQL copyright. As in, he feels that MySQL future will fall apart if there isn't a company that makes its money by dual licensing MySQL under some proprietary license. Amazingly enough Stallman, chief hater of all things proprietary, agrees. Hell seems to have frozen over. I however humbly disagree. The MySQL community has already left the dual licensing model behind. Sun has never shipped the "best" MySQL version, the community has!

Obviously since many of the patches that make the community versions better have not been licensed to Sun, they can't of course apply these patches to their distro without leaving their proprietary customers …

Here’s a quick flowchart for the different ways that Kontrollbase gathers and processes data.

We have lots of things on the go right now (over and above the normal process of keeping things up to date), and one of the main projects for me is to do a complete rebuild of the installation chapter (Installing and Upgrading MySQL). I’ll be starting with the 5.1 manual, then the 5.4 manual. Any future manuals should be based on these so we should be up to date for future generations. What I’m doing:

• Re-structuring the chapter to make it easier to follow on a platform basis. The old structure mixed content for different binary and source types, and different platforms, across a number of sections, making it very difficult to follow the instructions for your chosen platform.
• Make some things generic. There are sections which are generic and apply to all (or at least many) different installation types.
• Make some things …

We have lots of things on the go right now (over and above the normal process of keeping things up to date), and one of the main projects for me is to do a complete rebuild of the installation chapter (Installing and Upgrading MySQL). I’ll be starting with the 5.1 manual, then the 5.4 manual. Any future manuals should be based on these so we should be up to date for future generations.

What I’m doing:

• Re-structuring the chapter to make it easier to follow on a platform basis. The old structure mixed content for different binary and source types, and different platforms, across a number of sections, making it very difficult to follow the instructions for your chosen platform.
• Make some things generic. There are sections which are generic and apply to all (or at least many) different installation types.
• Make …

Feels like a long time ago, but my talk at the MySQL User’s Conference back in April 09 on running MySQL Multiple Times to get better performance is now available online at YouTube. The original PDF of the presentation is available here.View it here: YouTube – Improving Performance by Running MySQL Multiple Times

This entry is a follow up to TOTD #95 and shows how to use the recent integrations of JSR 299 in GlassFish v3 to convert a JSF managed bean to a JSR 299 bean (aka Web Beans). The TOTD #95 describes a simple Java EE 6 web application that uses Java Server Faces 2.0 components for displaying the results of a database query conducted by EJB 3.1 and JPA 2.0 classes.

The EJB class, which …

This entry is a follow up to TOTD #95 and shows how to use the recent integrations of JSR 299 in GlassFish v3 to convert a JSF managed bean to a JSR 299 bean (aka Web Beans). The TOTD #95 describes a simple Java EE 6 web application that uses Java Server Faces 2.0 components for displaying the results of a database query conducted by EJB 3.1 and JPA 2.0 classes.

The EJB class, which …

This entry is a follow up to TOTD #95 and shows how to use the recent integrations of JSR 299 in GlassFish v3 to convert a JSF managed bean to a JSR 299 bean (aka Web Beans). The TOTD #95 describes a simple Java EE 6 web application that uses Java Server Faces 2.0 components for displaying the results of a database query conducted by EJB 3.1 and JPA 2.0 classes.

The EJB class, which …