Open-source darling MySQL is facing a new uprising within its customer base over plans disclosed this week to reserve some key upcoming features, and their source code, for paying users of its namesake database.

Officials at Sun Microsystems Inc., which acquired MySQL in February, confirmed that new online backup capabilities now under development will be offered only to MySQL Enterprise customers — not to the much larger number of users of the free MySQL Community edition.

This will have very little effect on the Web development community, since we’re not the ones to use the high-end features anyway. It’s more targeted at making sure enterprise customers are truly paying for the product.

There’s really two ways this can develop:

1. From here on out, all “enterprise-y” features are only released to the Enterprise version of the product
2. There’s some delay, with these features eventually filtering to the Community version after some arbitrary time period has elapsed

Try as I might, I just can’t fault MySQL for this. Read this Wired article about the acquisition:

One analyst thinks MySQL’s annual revenue may come in at $70 million to $85 million.

“Less than 1 percent of MySQL users pay,” wrote Global Equities Research analyst Trip Chowdhry. “Users are in the habit of getting free stuff and it’s impossible to break the habit… We don’t see Sun (being) able to monetize it.”

Open source is wonderful, but there comes a point where a company has to turn a profit. Sun didn’t cough up $1 billion just for fun.

Amazon SimpleDB is a web service for running queries on structured data in real time. This service works in close conjunction with Amazon Simple Storage Service (Amazon S3) and Amazon Elastic Compute Cloud (Amazon EC2), collectively providing the ability to store, process and query data sets in the cloud. These services are designed to make web-scale computing easier and more cost-effective for developers.

Pricing is $0.14 per “machine hour consumed,” and about the same per GB data transfer both in and out.

When is someone going to come up with Fiction Markup Language -- an XML spec solely for annotating fiction?

Well, today I got an invite to a Google Group on this. Russell Warner is actually giving it a go, as detailed here. He seems to have a good start on it as well. There's a snippet of markup in there which looks really promising.

--i-am-a-dummy  Synonym for option --safe-updates, -U.

Yes, there is a MySQL switch called "i-am-a-dummy". It's an alias of another switch, which provides more information:

--safe-updates  Only allow UPDATE and DELETE that uses keys.

Now, that's handy. This means you couldn't accidentally wipe out your table because the system won't process DELETEs or UPDATEs that don't specify primary key values. Smart. It strikes me that the alias should be "i-am-not-a-dummy."

Look at it like this, PHPRunner is a lot like phpMyAdmin, but you can lock it down harder and pretty it up for non-database types.

How would you use this? Say I wanted to get a list of the number of comments posted every day on this blog. I could just use COUNT and GROUP BY to roll them up, but if there were no comments on a particular date, then that date just doesn't show up (since there's noting to count).

To get a "0" on date where there were no comments, I would need to join my original query on a table of dates. As it sits, I need to create this table and populate it and maintain it myself. Why couldn't this be built into a database platform?

There should be a table for numbers too. I was thinking about letters of the alphabet (but then you get into localization issues), days of the week, and months of the year. However, you can create those and maintain them easily, since they're finite. Dates and numbers stretch into infinity in both directions, so they're harder to deal with.

Does something like this exist on any platforms that you know of?

Using the GROUP_CONCAT function though, I no longer need to loop through them. I concatenate the list on the MySQL side, which returns me one record with one field.

I needed a good little XSL authoring app. XMLSpy is the absolute gold standard in this space, but it's also $400, which I didn't really want to pay. Additionally, it's huge. Hugely good, but bloated beyond belief.

The solution was a neat little open-source app called XML Cooktop. It was exactly what I needed: an interface that takes an XML file and an XSL file, and lets you transform the two with the click of a button. It shows you the raw HTML (well, XML -- whatever) it produces, as well as an embedded view of how the HTML would look in a browser (IE, mind you, but that's what I'm developing for in this case anyway).

Additionally, it has a nice little XPath debugger, kind of like The Regex Coach is for regular expressions.

It's lightweight, free, and does one thing really well. Exactly what I needed.

MSDE is stripped down in two ways.

1. It comes with no client tools, like Enterprise Manager or Query Analyzer. It's supposed to be a black box which your software knows how to operate, but you can't see into.
2. It's performance limited. It has a "workload governor" that "stalls" the app for a few milliseconds whenever it's fielding more than 5 - 8 connections (the exact number depends on the version).

The second limitation there may not be a big deal for an office scenario. In our case, the client has a dozen users that may or may not be connected at any given time, so the scalability limitations are never an issue.

The first limitation can suck, however. I don't like black boxes, especially when it comes to data storage. I want to know what's going on inside my database. To do this, I found a few tools that will do just this for the MSDE, and bring it ever so closer to SQL Server.

1. DbaMgr gives you a really nice graphic interface into your MSDE install, including databases, tables, users, and access to automated backup. It's free.
2. msde.biz is a site that sells two tools and gives one away. MSDE Query is free, and lets you run ad hoc SQL on your install, a la Query Analyzer. MSDE Backup does just that for $18, and MSDE Admin gives you a little Enterprise Manager goodness for $22.
3. SQL Buddy doesn't appear to be under active development anymore, but it's open source.
4. MSDE Manager might be a Cadillac of MSDE tools at $79. The screenshots look great.

Microsoft has a whole list of "MSDE partners" here.

So would the MSDE work for Web sites? I don't know -- it's certainly a step up from Access, but I don't use Access anymore either.

Another question about MSDE: with the advent of SQL Server Express -- the free version of SQL Server -- is the MSDE still going to hang around? Or are its days numbered? I can't find anything on "MSDE 2005," and if you Google for that, Microsoft has purchased AdWords to direct you to SQL Server Express, which would seem to indicate that it's a dead product.

Finally, for the record, while I've never been a big fan of Microsoft for server technologies, I've always liked SQL Server. My first official Microsoft training was an MCDBA track on SQL Server 7.0, and I've used the information I learned from that class six years ago over and over again since then.

Microsoft may not do everything right with servers, but SQL Server is a fine product, no matter how much you hate Redmond.

In this book, Celko illustrates several major approaches to representing trees and hierarchies and related topics that should be of interest to the working database programmer. These topics include hierarchical encoding schemes, graphs, IMS, binary trees, and more.

I paged through it at the bookstore. It's heavy on the nested set theory, rather than parent-child.

1. They buy Innobase, the company responsible for the back end data format that makes MySQL go.
2. They forge a partnership with Zend, the company responsible for PHP, which is the lanuguage most often used with MySQL on the Web.
3. Now, word via Slashdot and CNet, is that they're going to offer a free "Express Edition" of their 10g database.

They're not even trying to hide the fact that they're gunning for MySQL:

The new low-end edition is aimed squarely at free and open-source alternatives to Oracle's namesake database, said Andrew Mendelsohn, senior vice president of Oracle's server technologies division.

Here's my prediction for a secondary effect --

This action will ultimately lower Oracle DBA salaries. Oracle always had a huge barrier to entry in its price and infrastructure requirements, so you didn't run it unless you were in a big enterprise. Consequently, there are less Oracle DBAs in the world than other database platforms.

But now we're going to see a huge wave of people who know how to make Oracle go on a small scale. Companies will start hiring these people for less than a full-blown Oracle DBA salary, and either use them for smaller Oracle installments, or "train them up."

MySQL is now faced with the prospect of licensing technology they cannot ship without from their biggest rival. Interestingly, there's always been once piece of the InnoDB puzzle that's not available under the GPL: the InnoDB Hot Backup Tool. Without it, database administrators cannot backup their InnoDB tables without shutting down MySQL or at least locking out all transactions.

Oracle just bought themselves a whole lot of leverage with MySQL AB and a talented team of database engineers to boot.

I've always wondered why MySQL AB didn't buy Innobase Oy years ago. It always made complete sense from where I sat. But I'm hardly an insider when it comes to the relationship between those companies. Needless to say, that relationship just got far more "interesting."

What I need in a database is place where I can persist and retrieve data. Those are my requirements -- let me persist data somewhere, then let me get it back when I need it, in the form that I need it. Relational databases -- whoops, I mean SQL databases -- have allowed me to do this for years. And how exactly can that be so bad?

Dear Fabian uses these quotes as a supposed method of pointing out stupidity, but I utterly and completely stand by everything in the quote above. What I said was true then, it is now, and it will be in the future no matter how much Fabian wishes it not to be so.

Something even cooler: I'm number six on Google for "Fabian Pascal." Fabian has been fantastic for my traffic.

(Note: the quote rotates, so the link above won't show the quote forever. Eventually we'll be relegated to the past quotes page)

I'm surprised by how bare-bones MySQL is. I knew it was stripped down, but it looks worse when you see it laid out like this.

The following tables compare how different DBMS products handle various SQL (and related) features. If possible, the tables also state how the implementations should do things, according to the SQL standard.

Just reading this will teach you something you didn't know about your preferred platform.