Welcome, to the 31st edition of Log Buffer, the weekly survey of database blogs. The DB2 world is a good place to begin. On Monday, Craig Mullins published a DB2 for z/OS status check, What’s Up With DB2 Today? on his Perspectives on Database Management: “I thought it might be useful to examine what [...]

The MyBlogLog team is looking to grow and we could use a few good engineers. We're currently on the hunt for a good general purpose LAMP engineer: someone who knows their Apache, PHP, Perl, MySQL, and related stuff.

This job is ideal for someone who lives in San Francisco, Berkeley, or Oakland and wants to work on a small team that's continuing to build a service that's growing very quickly and has very passionate users. We have lot of new hardware to play with, a great office, and tons of ideas about where to take the service.

The Yahoo! office is located on University Ave, just a few blocks from campus and the local BART station. There's also an amazing selection of eateries just outside the front door.

Send me your resume if you're interested.

We're also …

I just thought I might link to an article on RegDeveloper called MySQL is the company's SQL now...

Go read it yourself, it is rather short, but interesting nevertheless. I especially like the sentence at the bottom: It remains to be seen whether the company fully understands, and can cope with, the culture shock it is about to suffer; as callers change from 'friends' to 'customers'.

This is what I have been thinking about too, when they started releasing enterprise builds more often than community builds (binary builds that is). In the past MySQL always suggested to use the binaries provided by them to rule out any effects that may be introduced by a 3rd party build process or patches. That made much sense to me.

However now they tell you that you can check the source …

I just thought I might link to an article on RegDeveloper called MySQL is the company's SQL now...

Go read it yourself, it is rather short, but interesting nevertheless. I especially like the sentence at the bottom: It remains to be seen whether the company fully understands, and can cope with, the culture shock it is about to suffer; as callers change from 'friends' to 'customers'.

This is what I have been thinking about too, when they started releasing enterprise builds more often than community builds (binary builds that is). In the past MySQL always suggested to use the binaries provided by them to rule out any effects that may be introduced by a 3rd party build process or patches. That made much sense to me.

However now they tell you that you can check the source …

I happened to run across a software company called LabKey recently.  A former colleague of mine from way back when, Adam Rauch, started doing work at the Fred Hutchinson Cancer Research Center a few years ago where he developed a system for analysing mass spectrometry data.  Adam was one of the original team at Microsoft that created Visual Basic and went on to create some other pretty amazing products there. 

LabKey developed the CPAS (Computational Portal and Analysis System) software as an open source science project offering web-based bioinformatics and collaboration tools to help scientists store, analyze, and share data from high-throughput experiments and observational studies. The Fred Hutchinson Cancer Research Center uses CPAS to …

In Part 1 of this article series, we looked at how the Falcon transactional storage engine was architected and how it compared to some of the other MySQL storage engines. In this article, I?ll focus on how Falcon performs transaction management, including some special points on where Falcon differs from some of MySQL?s other transactional engines.

As of MySQL 5.0 there is no SHOW CREATE TRIGGER which is pretty annoying. I don’t like using “show triggers like
“, so I figured I’d write a wrapper around mysqldump. For the record, this was a huge pain the ass. I did this on Fedora, GNU sed version 4.1.5. You need to have your password stored in ~./my.cnf for this to work, I believe. I haven’t tried it without it.


mysqldump -dnt database | sed "/\/\*\!4.*\*\/;*/d" | sed "s_/\*\!5[0-9]*__g" | sed "s_DEFINER=.*\*/__g" | sed "s/\*\/;*//g" | sed "/SET/d" | sed "s/^[ \t]*//" | sed "s/\ \ */ /g" | sed "/--/d"


You will get a dump of ALL the triggers in your database, using this. However, since that’s what I need on this particular example, it’s what I’m sharing. I’m sure I could have cleaned up the code a little and used fewer calls to sed, but frankly I don’t mind, since it works fine.

I hope this helps someone.

If you're in the L.A. area, this weekend I will be speaking at the Southern California Linux Expo (SCALE) on SQL coding, schema and index tuning MySQL servers. Come meetup with me at the MySQL BoF or find me around in the sessions.