But there are still a few things to do before it can go stable. I reworked the client and admin roadmap the other day. I moved a couple items to a post 1.0.0 release. Specifically I moved the cache advances, session abstraction and expanded perm XML container. However if anyone steps up who has an immediate need for these features and does significant code contributions, these features could still of course be fast tracked to be included into 1.0.0 stable.

Its done! After more than 2,5 years pondering on the design decisions in MDB we finally have a successor MDB2 with a first stable. Along with it the ibase, mysql, mysqli, mssql, pgsql, sqlite drivers have been marked stable.

A long while ago I added a seemingly idiotic feature to MDB2: The ability to disable the execution of queries.

The following is a little SQL challenge I have so far been unable to complte myself. Lets say I have a table with transactions for different products.

I am not sure why this thread ended up on the pgsql hackers list, but nobody took any measures from stopping it and instead a very interesting and detailed discussion of the pros and cons of surrogate keys in RDBMS schema design ensued. So this thread should be of interest to anyone using an RDBMS be it MySQL, PostGreSQL, SQLite or any other alternative.