I had a long flight from Sydney to Edinburgh this weekend, and wanted to answer a common training question - how fast/slow is the stored proc language in MySQL. To do this, I started by stealing an example exercise we have in one of our exercises:


DELIMITER //
CREATE FUNCTION fibonacci(n INT)
RETURNS DOUBLE
NO SQL
BEGIN
DECLARE f1, result DOUBLE DEFAULT 0.0;
DECLARE f2 DOUBLE DEFAULT 1.0;
DECLARE cnt INT DEFAULT 1;
WHILE cnt <= n DO
SET result = f1 + f2;
SET f1 = f2;
SET f2 = result;
SET cnt = cnt + 1;
END WHILE;
RETURN result;
END //


If I run this a few times, here are the results:

mysql> select benchmark(100, fibonacci(40000));
+----------------------------------+
| benchmark(100, …

I’d like to inform members of the MySQL™ Community about an amazing Program @ Sun™ Developer Network: the Campus Ambassador Program.

Quote:
Sun has more than 500 campus ambassadors worldwide who help spread knowledge and awareness of leading-edge technologies such as Java™, NetBeans™ IDE, OpenSolaris™, and many more.

Now that MySQL™ is part of SUN™ I guess that you can be ambassador of MySQL™ too, among the other SUN™’s products.

Quote:
Campus ambassadors are Sun™ Microsystems interns who build a Sun™ community on their school or university campus. They learn all about the latest Sun™ open-source technologies and share that knowledge with fellow students. This includes activities such as starting a Sun™ user group on campus, demonstrating Sun™ technology to fellow students, …

The GSoC is about to end up and it is time to sum up what has been done within the last weeks.

News

*Error handling added. Plugin uses the following mechanism to gather and report errors. When we can't load/open SIGAR library or get any information from it we pass the error to user informing about that. On the other hand when only some information is not available we rather print warning about that to MySQL .err file.
Also we check for return value for each schema_store_record function.

*Plugin has been merged into the MySQL 6 server code. Now you can download and compile the MySQL server with SIGAR plugin already being there.

Downloads

Standalone SIGAR plugin is available at lp:~m.ch/mysql-server/sigar-plugin.
SIGAR plugin merged into the MySQL server is available at lp:~m.ch/mysql-server/mysql-6.0-sigar-plugin.

Updated installation …

I'm off to do some MySQL training in Asia for the rest of the month. One week in Singapore, one week (and the weekend) in Bangalore.

Correction, Asia and the Emerging Markets. Apparently thanks to phenomenal growth, China and India have left Asia in the last few years (in our corporate parlance).

Always good to check flight status before you head to the airport, even (especially?) at 7am when you just checked 6 hours before. I now have 5 extra hours in beautiful John F Kennedy Airport, terminal 7. I haven't seen the new JetBlue terminal, but this one almost makes JFK feel like a major international airport.

Cathay Pacific seems a fine airline, though perhaps …

I'm off to do some MySQL training in Asia for the rest of the month. One week in Singapore, one week (and the weekend) in Bangalore.

Correction, Asia and the Emerging Markets. Apparently thanks to phenomenal growth, China and India have left Asia in the last few years (in our corporate parlance).

Always good to check flight status before you head to the airport, even (especially?) at 7am when you just checked 6 hours before. I now have 5 extra hours in beautiful John F Kennedy Airport, terminal 7. I haven't seen the new JetBlue terminal, but this one almost makes JFK feel like a major international airport.

Cathay Pacific seems a fine airline, though perhaps …

I'm off to do some MySQL training in Asia for the rest of the month. One week in Singapore, one week (and the weekend) in Bangalore.

Correction, Asia and the Emerging Markets. Apparently thanks to phenomenal growth, China and India have left Asia in the last few years (in our corporate parlance).

Always good to check flight status before you head to the airport, even (especially?) at 7am when you just checked 6 hours before. I now have 5 extra hours in beautiful John F Kennedy Airport, terminal 7. I haven't seen the new JetBlue terminal, but this one almost makes JFK feel like a major international airport.

Cathay Pacific seems a fine airline, though perhaps …

I'm pleased to announce the release of DBD::mysql 4.008!

This release contains several fixes, particularly the issue where TAKE_IMP_DATA_VERSION being defined allowed code features to be compiled in that caused potential grief for anyone running DBI < 1.60x (segfault). I've disabled this for the time being until I find a better solution.

I've also decided from now on, as soon as I get a patch, or if I fix something, even if it is a minute change, I'm rolling out a release. Release early and often, right!?

The changes in this release are:

* Multi statement patch (fixes multi statement issues), thanks to Chris Heath!
* Disabled TAKE_IMP_DATA_VERSION because segfault with DBI < 1.607
* #29528: bind_param(..., SQL_FLOAT) ignores exponents - fixed, Thanks to
Tokuhiro Matsuno!
* Cleanups to make mysqlEmb work under Cygwin - Thanks to Chris Rodgers
…

Agenda:

* CAOS Report 8 - Community Linux
* Linuxworld review
* A look at SourceForge
* Microsoft’s new database push

iTunes or direct download (26:48, 6.1MB)

I have been asked twice this week what version of MySQL I would choose for a new project.
As with most questions in life the answer is: It Depends?

In general I would now recommend for a new project to select 5.1, and he is why.

1. If it’s a new project and your not managing existing applications with older versions then 5.1 is slated for General Availability (GA) at some imminent time. Having been at Release Candidate (RC) for quite some time (almost 1 year), many people, both internally and in the community are just waiting for Sun/MySQL to get this version out.
2. MySQL 5.0 is in maintenance mode, it’s now 3 years old. MySQL is placing (I’m assuming) resourcing energies to current and future releases.
3. If your looking at releasing a product in the next 3 months for example, you do not want to consider the testing and deployment of a new version (e.g. 5.1) in the next 6-9 months.
…

Welcome to the 110th edition of Log Buffer, the weekly review of database blogs.

From the MySQL side, Jeremy Zawodny gets things going this week. He writes about his doubts over the long-term performance of InnoDB, specifically the cost of multiversion concurrency control, particularly in a master-slave arrangment or a DW. Jeremy comments, “[The] disk bloat, fragmentation, and ongoing degradation in performance may be an argument for having some slaves that keep the same data in MyISAM tables.” His readers, however, point out some diagnostics and tools to remedy this concern.

Not that MyISAM is without foibles. Case in point, on the …