We introduced a new library to use with our update-feature inside Workbench. With the new lib (yassl) it’s possible to use SSL encryption for the authentication/download of new SE releases. This was not possible with libcurl because we’re not allowed to use/bundle openSSL. As this update is included staring with 5.0.22 all SE users will have to download version 5.0.22 manually from the enterprise pages one more time. Please logon to https://enterprise.mysql.com/software/gui_tools.php with your mysql username and password, download the latest release and launch the installer manually. Sorry for the inconvenience.

The parameter DiskSyncSize is a MySQL Cluster parameter and was added in MySQL 5.1.23.

After the amount of stored bytes of data per file, the data node will fsync (flush) the LCP file to disk, even if a fsync is not needed for consistency.
This is done because the OS will otherwise buffer all the writes, and when a fsync is really needed, it can take a lot of time...

Originally this parameter was hard coded. Now it defaults to 4 Mbyte.

The parameter DiskSyncSize is related to the parameters NoOfDiskPagesToDiskAfterRestartTUP and NoOfDiskPagesToDiskAfterRestartACC which are deprecated right now. It does NOT replace the parameter TimeBetweenLocalCheckpoint.

This parameter should not be changed on any OS (with reasonable settings). With ODIRECT it is not used at all.

Thanks to Jonas for the help.

I'm proud to announce that after significant wrangling (just suggesting did the trick, actually ;-), I've found Sebastian Bergmann willing to visit Australia, and teach a 3-day workshop Quality Assurance in PHP Projects. It's scheduled 4-6 August in Melbourne.

Many applications using MySQL are written in PHP... this three-day workshop will introduce PHP Developers to writing unit tests for the backend and system tests for the frontend of a web application as well as managing the quality from development to deployment and maintainance using tools such as PHPUnit, Selenium RC, phpUnderControl, PHP_CodeSniffer, and …

The parameter DiskSyncSize is a MySQL Cluster parameter and was added in MySQL 5.1.23.

After the amount of stored bytes of data per file, the data node will fsync (flush) the LCP file to disk, even if a fsync is not needed for consistency.
This is done because the OS will otherwise buffer all the writes, and when a fsync is really needed, it can take a lot of time...

Originally this parameter was hard coded. Now it defaults to 4 Mbyte.

The parameter DiskSyncSize is related to the parameters NoOfDiskPagesToDiskAfterRestartTUP and NoOfDiskPagesToDiskAfterRestartACC which are deprecated right now. It does NOT replace the parameter TimeBetweenLocalCheckpoint.

This parameter should not be changed on any OS (with reasonable settings). With ODIRECT it is not used at all.

Thanks to Jonas for the help.

I've been a little out of touch lately -- crazy accounting project for school -- but was able to carve out a little time to chat with the guys at Engine Yard who are doing some cool things with Ruby. Engine Yard employs Evan Phoenix, the founder of the Rubinius project. The project aims to deliver a virtual machine for Ruby and will be previewing Rails running on Rubinius at RailsConf 2008 later today. According to Evan, Rubinius is an implementation of a Ruby platform, just like the standard Ruby interpreter, IronRuby, MacRuby, JRuby, or countless other implementations. What's interesting... READ MORE

During the webinar "Highly scalable solutions with MySQL and Memcached" Ivan Zoratti announced that Sun will support Memcached as a part of MySQL Enterprise Support.

You may want to check you the white paper "Designing and Implementing Scalable Applications with Memcached and MySQL"

There is another webinar later on today (Designing and Implementing Scalable Applications with Memcached and MySQL), so if you missed out on yesterdays …

We’re looking for experienced OO-PHP programmers. Read all about it here (in Danish only; sorry ’bout that).

As of today, the third, final and largest code release for Open High Availability Cluster has been made available.  This now means that all of the Open HA Cluster code is available as free software.   This will allow developers and admins to access and build complete HA solutions built on source code from the OpenSolaris project.

Right before the launch I grabbed some time with Meenakshi Kaul-Basu, the engineering director at Sun responsible for Availability products, and whose group the Open HA Cluster falls under.  Take a listen to Meenakshi's explanation of the event and her insight:

My interview with Meenakshi (9:29)  …

MySQL Server does not require you to specify name of the index if you're running ALTER TABLE statement - it is optional. Though what might be good practical reasons to specify the key name or omit ?

Things what you should be looking at is how MySQL names indexes automatically as well as what maintaining the indexes.

Lets first speak about naming. If you do not specify index name MySQL will name index by the first column of index created, if there is such index already it will add numeric suffix to it, for example:

PLAIN TEXT SQL:

1. mysql> CREATE TABLE t1(i int, j int);
2. Query OK, 0 rows affected (0.01 sec)
3.  
4. mysql> ALTER TABLE t1 ADD KEY(i,j);
5. Query OK, 0 rows affected (0.03 sec)
6. Records: 0  Duplicates: 0  Warnings: 0
7.  
8. mysql> ALTER TABLE t1 ADD KEY(i);
…