My thoughts are with Londoners this morning.

There’s a new $100 million fund that’s going to invest with companies producing products that are related to a certain kind of XML document. (Via Seth Finkelstein.)

Earlier this year I mentioned that I don’t learn best how to do something new from books. Getting my hands dirty works better from me. However, there’s nothing like a good book to cement and round out your knowledge of a subject once you’re already proficient. Recently I read two books that really helped me in this regard. The first was Jeremy Zawodny and Derek J Balling’s High Performance MySQL, the second was Hibernate in Action from Christian Bauer and Gavin King.

Hibernate is a persistence layer for Java. Basically, you define some mappings from your Java classes to your database, and Hibernate takes care of all of the messy work of generating your SQL for you, not to mention the even messier work of dealing with JDBC. Much as I love SQL, Hibernate is a huge labor saving device, and it makes it a lot easier to deal with your object model in a truly object-oriented fashion. I’ve been using it successfully for real projects for a few years, but I always felt like I was just scratching the surface of what could be done with it. I had also run into some performance issues here and there. Anyway, Hibernate in Action came highly recommended, and deservedly so. Not only does it document Hibernate incredibly well, but it also explains a heck of a lot of the theory behind relational databases and object-relational mapping as well. It’s a truly outstanding book.

I read High Performance MySQL out of desperation. I’ve been using MySQL for a really long time, but recently I had run into some performance issues that I needed to resolve, and I wanted to learn about all of the things I could do to address them. What I learned is that the book should really be called, “How to be a MySQL DBA.” That’s a good thing. The book does discuss indexes, performance tuning, clusterning, replication, and all of the other topics you want to address if your database is too slow, but it also goes into other stuff like backups, security, and how the different database engines work. The explanation of the difference between MyISAM and InnoDB is worth the price of admission alone.

To make a long story short, I recommend both of these books highly. Now I’m going to read a novel.

Sam Ruby is calling out Apple for releasing iTunes with a screwy RSS parser and Disney for publishing feeds that fall into the traps set by the parser’s quirks.

Sarah Vowell in the New York Times:

That fact, that every three seconds an African human being dies from hunger or AIDS or, honestly, mosquito bites in this day and age, is literally the dumbest thing I’ve ever heard. Way, way, way dumber than that thing about Orlando and a meteor from God. That every-three-seconds statistic is so moronic, and having the richest countries in the world do something about it is such a total no-brainer, that Pat Robertson will join up with Dennis-bloody-Hopper of “Blue”-bloody-“Velvet” to spread the word.

This is a solvable problem. Think we have the will to solve it?

Technorati may be on a roll, but their search engine doesn’t work very well as far as I’m concerned. Maybe sucking least is the key to their success? Every time I try to use Technorati I find it to be slow and inaccurate, but I don’t know that any of the alternatives work any better.

Further proof that Rodney Dangerfield was really a Unix sysadmin.

Paul Boutin says Jorn Barger is now homeless in San Francisco. Jason Kottke reports that Jorn denies the story.

Update: Jorn’s denial is on the talk page for his Wikipedia article.

A couple of weeks ago, I mentioned a way to improve the performance of MySQL queries by avoiding the use of the lower() function to provide case-insensitive matching. (I suggested the use of LIKE without wildcards.) A couple of people have written to mention that by default, the = operator is not case sensitive in MySQL, so an expression like 'Houston' = 'HOUSTON' will be a match. For other databases, the LIKE thing is probably still good advice.

Most major PHP-based blogging packages have a major security hole that can be exploited. I’m glad I haven’t switched to anything yet.