The Drizzle database, while similar to MySQL includes a number of significant differences. In this post we will look at data types and table syntax that is valid in Drizzle. For more background information you can also review A beginners look at Drizzle - Getting around with SHOW.

Data Types

This comparison is with Drizzle 2009.03.970 and MySQL 5.1.32 GA. More information at MySQL 5.1 Data Types.

The following data types are not valid in Drizzle.

• TINYINT
• SMALLINT
• MEDIUMINT
• BIT
• TIME
• YEAR
• BINARY
• SET
…

As a fitting posting for April 1, here's a video that I put together to commemorate Marten Mickos, CEO of MySQL who is leaving Sun today. It was my pleasure to work with Marten for more than five years at MySQL. He was truly a unique CEO; he followed Drucker's rules and came up with new innovative ideas that we put into action.

read more

Just saw this story on Slashdot which made me think of this post from Marc Fleury.

The Slashdot story questions what/where is the official MySQL tree:

read more

Assuming you have successfully compiled Drizzle, and you are ready to start for the first time, here are some beginner differences with those familiar with the current MySQL 5.1 GA version. Note: drizzle is actually an original fork of the 6.0.x codebase however the code looks very little like mysql anymore.

Getting started differences

The first default MySQL installation step scripts/install_mysql_db is gone, and there is no replacement. The ‘mysql’ schema no longer exists. Talking about schemas, ‘test’ is also gone by default.

While a bin/drizzled_safe exists to start drizzle, this presently doesn’t operate as expected. You should start drizzle with sbin/drizzled &

They still have an empty …

I’ve not looked at compiling and running Drizzle on my server for the past four weeks. Well overdue time for a check and see how it’s going. I saw in today’s planet.mysql.com by Eric Day a new dependency is needed. libdrizzle 0.2.0 now in Drizzle is now required, so I started there.

cd ~/bzr
bzr branch lp:libdrizzle
cd libdrizzle
./config/autorun.sh
./configure
make
sudo make install

No problems there, also documented at the Drizzle Wiki. Great to see the docs up to date. I see my old work on starting the compiling page still relevant. Tested on CentOS 5 and Mac OS/X 10.5

Compiling drizzle was not much more difficult.

cd ~/bzr/drizzle
bzr update
make distclean
./config/autorun.sh
./configure --prefix=/home/drizzle/deploy …

Taking the work already done with vmplot.sh, a useful tool for MySQL performance tuning by Yves and Matt at BigDBAHead, and in true Open Source fashion I’ve enhanced and modified for my own purposes.

These changes include:

• Error checking for ‘gnuplot’ command on the system
• Eliminate the first row of sample data, as this is often not a complete sample for the vmstat duration.
• Created a HTML output file for easy browser viewing
• Changed Memory scale values from Kilobytes to Megabytes
• Resizing png’s for optimal 1024×768 display output (2 per row)

Download vmplot

And I get:

So more specifics of what I did.

Install gnuplot.

$ yum install gnuplot

Create vmstat sample …

The numerous popular MySQL forks are an unexpected consequence of Sun's acquisition. But why haven't we seen any JBoss forks since the Red Hat acquisition? READ MORE

This week, I'm finishing up my book "Developing Web Applications using Perl, memcached, MySQL and Apache". I just finished up Chapter 1, which is the first chapter where I discuss several things such as how much things have changed in the last ten years with web development and Open Source in general. This lead me to write a small section about the future. I was pondering -- where are we going to be in ten years from now? What projects will be popular? This lead me even to a more specific question, and one that I would ask here: what is to become with the development of MySQL? What will be the official development branch of MySQL, and where is all the energy and excitement going to be around?

There is now one fork and one major branch of MySQL now that I will mention, both are exciting projects-- and neither of them is coming from official MySQL/Sun:

(The order of these is strictly alphabetic and not priority!)
…

As mentioned previously, Monty Widenius is starting his new company based on some interesting premises. With Zak Greant they have co-authored a pamflet where they outline a blueprint for Open Source companies. In many ways this could be considered the "Dogme 95" of Open Source businesses:-)

read more

Reading “Test Center: Slacker databases break all the old rules” has finally inspired me to write this post, which I’ve been meaning to do for a while. The title of my post may be bold, but it is just one version of how things may go moving forward (and was meant to grab your attention). :)

First off, a few issues I have with the article mentioned above:

• “…tacking the two letters “db” onto a pile of code that breaks with the traditional relational model.” - Since when does a database need to be relational? Sure, relational databases are the most popular, but they are only a subset of all the possible database types (let’s not forget hierarchical or tuple stores).
• “None of them is right for everyone, and all of them are completely …