bilbo

Thanks for the reply. It does seem that multiple database support was in the plans at one time.

The reason that I asked the second question is that, while I could write a “forked” version, I have no desire to create an offshoot of WordPress. I would prefer to see a unified version that was not tied to one database, however applicable that database might be. I have been looking into doing exactly that (though it is not trivial by any means). If such a task were to be performed, would they simply shrug it off though as “nice, but not really useful?”

I understand what you mean regarding SQL dialects. One solution to that would be to abstract any SQL into the data access layer and create methods that WP used, such as $wpdb->get_posts_for_date('<some date>') instead of $wpdb->query( "select * where date='<some date>').