Yes, that's correct, it's not a typo. Who needs XML over RDBMS?
So far, there has been a relatively small group of users who were demanding more XML features within or combined with MySQL. Perhaps it's because XML is not a big deal in the classic LAMP implementation of web-based services, but the more we penetrate the Enterprise market, the more XML is becoming an interesting topic. I am quite sure that we will move from the classic "nice to have" to the typical "commodity feature" in quite a short time, especially if we will improve our presence as the back end DB for J2EE apps and web services.

Let's be honest, the new nice XML features in 5.1 are still away from a good and proper XML coverage. They are great if we are going to store XML elements within columns of a table, but they are not really helpful if we need to use an XML interface to interact with our DB.

For what it's worth, although the fat 4 (Oracle, …

There is a big event for the London Meetup Group coming up next week. We will all meet on Wednesday 5 March @ 7pm
The location: The Lamb
4 Lambs Conduit St
Bloomsbury
London
WC1N 3LZ

We will have a very special guest: Marten Mickos, CEO of MySQL (now in his new role, due to the Sun acquisition). Marten will join us and he will be happy to answer to questions, to share opinions and spend some good time with MySQL Brits users in front of a nice drink (no surprise which one will be the best seller :) ).

From a technical point of you, I have prepared a short presentation on MySQL Proxy, with a basic intro on the project and with some ideas on how to use it and what to expect from a production version. The slides will be uploaded after the venue.

As usual, I am open to suggestions and topics to …

The only thing worse than being talked about is not being talked about --Oscar Wilde

The table below shows the popularity of the data warehousing tools as determined by the number of the Google search results. There are only a few surprises, and you can easily arrive at your own conclusions. Just keep in mind that popular does not necessarily translate into good1.

At $WORK we typically use Redhat Cluster to make MySQL highly available. We have a number of 2-node clusters (active/passive) and it works nicely, for the most part. One thing I find very annoying is RHCS has no notification framework to notify you when a service is relocated to another node (because of failure or otherwise.)

In a perfect world, the only reason MySQL would pass between nodes is for server maintenance, under the control of a human. In reality, crap happens. Redhat Cluster manages all this, but I still want to know that a failover happened (is hardware going bad? did a software bug cause a failure? etc.)

Most monitoring tools weren’t designed to report on a clustered service. I can add a check that connects to MySQL using the cluster-managed IP - but that only tells me if MySQL has failed completely. The failover between nodes generally takes under a minute so it’s easy for that type of monitoring check to miss a …

Alfresco's CEO, John Powell, wants and expects Alfresco to IPO. He thinks it will show the world that open source offers long-term staying power. John Roberts at SugarCRM is disappointed that MySQL didn't go public to provide evidence that open source is a viable business phenomenon.

Good points. ...

For years, MySQL never supported query cache with prepared statements. When I initially implemented MySQL prepared statements and its associated C API in MySQL 4.1 version; prepared statements were just saving the parsing cost of the query and nothing much. But now, the things are totally different.

Lot of developers stayed away from prepared statements due to this limitation (atleast for select statements). But now the latest MySQL 5.1 server does support the caching of prepared statements with …

Maybe there's still some fight in the PostgreSQL competition, after all. [Update: Or maybe it has more to do with internal changes at MySQL - see below.] According to data compiled by MarkMail, PostgreSQL messaging traffic dwarfs that of MySQL's, suggesting that the Postgres community is more active than MySQL's:

Comparing PostgreSQL and MySQL is kind of interesting. With all the talk about the LAMP (Linux/Apache/MySQL/PHP-Perl-Python) architecture you'd think MySQL had a lock on the open source database market, but based on simple message traffic analytics, PostgreSQL has a much higher level of community involvement. Looking at January 2000 onward, the MySQL lists have amassed 340,000 messages with about 3,000 new messages each month. In the same time period, the PostgreSQL lists have hit 583,000 messages with 7,000 new each …

As already reported the deal is done (see Sun Press Release, Kaj - Ambassador to Sun comments). I’ve had a look at the Official Sun-MySQL website.

Here is a review of the interesting words and images on the new site.

• Overview - Ultimate Scalability for the Web Economy (dolphin & sunset)
• Features - It Just works (windsurfer with island view)
• Tech Specs - Celebrate the Possibilities (skydiver on snowboard)
• Perspectives - Open, Fast, and Free Just Got Better (snowboarders viewing the mountain scape)
• Support - Unbeatable Duo - Open Source and Global Support (couple showing the V symbol)
• Training - Get Trained. …

As already reported the deal is done (see Sun Press Release , Kaj – Ambassador to Sun comments ). I’ve had a look at the Official Sun-MySQL website. Here is a review of the interesting words and images on the new site.