While we have been building these packages internally for quite some time already (we received our Transition Kit in July), the packages of MySQL for OS X on Intel (Mactel) can now be downloaded from our our download pages.

The "port" to OS X on Intel was actually quite trivial: "configure; make"... We only had to fix a few trivial cosmetical issues. As the code itself has already been ported to Mac OS X on PPC and also builds on other x86 platforms (Linux, *BSD, Solaris), we did not really expect any portability issues.

Note however, that these currently are no "Universal binaries" - they only run on x86. Downlad the PPC binaries, if you have a regular G4/G5 Mac.

Now the first alpha release of partitioning has been released.
This includes more or less all the syntax for partitioning to be
available. There is still some optimisation patches that are in the
works for coming 5.1 alpha releases.

There is still a small window of opportunity to get smaller additions
in so please use the MySQL partitioning forum to feedback any ideas
you have on improvements.

Partitioning is designed to work with all storage engines of MySQL. It is
however not possible to mix storage engines in a table. It is also possible
to use partitioning for MySQL Cluster. This gives the DBA the possibility to
control data placement in the cluster and thus create heterogenous clusters.

Most of the documentation for partitioning is already written and can be found
in the MySQL 5.1 Reference Manual due to some hard work by Jon …

I promised I would start posting some previews of what we're selecting for our next users conference.

The first selected session to tell you about is Technorati, which indexes the real time web (blogs/news) and operates on a "never delete anything" basis. You can just imagine what the consequences of this are ;-)

I actually kind-of already preselected this talk during the 2005 users conference, and this is because of the speaker: Dorion Carroll, Senior Engineer at Technorati. He really stuck out in the "Scaling and High Availability" panel, showing off excellent speaking and presentation skills. So after this panel session, I "told" Dorion straight away that we would definitely want him to speak at the next conference... so here we are! ;-)

More previews to come!

I promised I would start posting some previews of what we're selecting for our next users conference.

The first selected session to tell you about is Technorati, which indexes the real time web (blogs/news) and operates on a "never delete anything" basis. You can just imagine what the consequences of this are ;-)

I actually kind-of already preselected this talk during the 2005 users conference, and this is because of the speaker: Dorion Carroll, Senior Engineer at Technorati. He really stuck out in the "Scaling and High Availability" panel, showing off excellent speaking and presentation skills. So after this panel session, I "told" Dorion straight away that we would definitely want him to speak at the next conference... so here we are! ;-)

More previews to come!

MySQL AB has been selected as a technology partner for development of Alcatel's future carrier-grade multimedia communication products. Under the agreement, Alcatel will use the high-availability MySQL Cluster database as the repository for key subscriber information, which has to be available in real time whenever a phone call is made or any network service is accessed.

MySQL 5.0 has been downloaded over four million times: two before GA, and two after GA. We’re proud of these numbers. But life does not stop at MySQL 5.0.

So we have now announced the first public version of MySQL 5.1 alpha. Remember, alpha at MySQL means that we’re still adding features.

One of the hottest new features is partitioning. Partitioning allows distributing portions of individual tables across a filesystem, according to rules which can be set when the table is created.

In effect, different portions of a table are stored as separate tables in different locations - but the user still sees the partitioned table as a single table.

If you have datasets of several …

(Third part of the MySQL 5 general purpose routine library presentation.)
How many times, while using a MySQL client, you were facing a problem that seemed quite simple to solve, if only you could perform a loop of some sort without creating an external script?
I often found myself doing things like

$ for $X in `mysql -B -N -e 'show tables'` ; \
  do perl -pe "something with $X" |  \
  mysql -e "something else with $X" ; done

Or perhaps I write a quick Perl script to achieve the result I need. But how much better it would be if I could use a FOR EACH loop from mysql command line! Hence, when stored procedures became available, I started planning this kind of features, and now I can say that I have made my life simpler with these powerful language extensions.

complete, normal, simple. …

So this is the plan. Welcome to Dial-A-Monkey!

Do you need to give out a phone number from time to time? Would you like it so that the tele-marketer gets an earful when he dials?
Try giving out this: 360-226-7186

I actually have two numbers right now, the above, and a secret one. The secret one is being fed directly into my Asterisk server's blacklist. I am giving it out as my home number whenever I sign up for free stuff. This number, 360-226-7186, I am letting anyone use. I won't blacklist from people who call it, so feel free to play with it.

So how am I doing this for free? (ok, minus my time, a computer, some electricity, and the anger of those around me for not leaving the house on a Saturday).

Go to http://www.freeworlddialup.com/ and get a number.
Next go to sourceforge and install Asterisk@Home. For what I …

Every so often I look at a piece of code and figure out something clever. In the current case I just figured out how to avoid a memcpy () per row read during a scan in MySQL. Problem with my solution? You need to make sure the structure that is being poked is never reordered. It is fine if someone adds new elements, but just not between these two items.

For safety I could wrap these two items in a sub structure just to make sure that no one gets clever.

I've put up comments all over the code pointing out that juggling this structure will cause issues.

Doing this will save 12bytes of allocation and on a million row table a million memcpy() calls (which do add up). Memory speed is not following Moore's law, so you need to think about cost of moving it around. Its not free.

Someday, someone will ignore the comments, and blow their foot off.

Thankfully there is a test case which …