� NAACP Career Day | Main | Podcasting �

May 6, 2005

Berkeley db defeated

I have finally conquered the dreaded db known as Berkeleydb. Most of my experiences with db have been fraught with peril and uncertainty. In the past, I had used db for Evolution, the drop in Open Source replacement for M$ Outlook. If my memory serves me well, I seem to recall that db isn't backwards compatible. So each time the db developers upgrade their software, the previous version simply do not work as designed. I distinctly remember being told by GNOME developers, that I was to use db-3.17 and _only_ that version, as all others would not work correctly,.

More recently, I seem to have corrupted my blog database. It seems that I ran out of space on my server, so the db could not be properly parsed by the MT publishing engine. I received a couple duplicate entries and many 'serialized' errors after rebuilding my entries.

So, I decided to simply migrate the default db to the more robust mySQL. I won't go into the gory details here, but I did find alot of help by using the ubiquitous 'google' search. It appears that many other MT users have also experienced problems with db. Immediately following the migration, I noticed a tremendous performance boost in the rebuild process. I no longer receive timeouts etc.. No more serialize..pm errors either.

The question I have for Ben Trott et al at Six Apart is "Why use such a fragile db?". If the db isn't robust to adverse conditions (file locking, mismatch parsing errors, etc), it should not be the default database for the publishing engine. Why not use mySQL as the default?

Anyway, I'll stop my mild 'rant' here. I've slayed db dragon, and I am better for it. Now, I can begin to post entries more frequently, and make up for any lost time.

I'm back on the block like Quincy Jones.

Posted by AG at May 6, 2005 6:33 AM