So it seems that my original plan of just a few RCs for MDB2 did not go through. I am now at RC4. I have spend alot of time over christmas just reading the source up and down. That way I found a number of bugs and ugly spots that I fixed within those 4 RCs.

Personally last year was very interesting. Not necessarily successful, but enlightening on so many levels, that I am sure 2006 can only be a success. Now over the last few days I afforded myself the luxury (or torture) to look at other peoples code, besides pushing out one RC after another on MDB2 and related packages. Specifically I looked at some of the latest ActiveRecord, CRUD in no time, hyped up frameworks: QCodo, Cake and Symfony.

I just wanted to show case some of the new features in MDB2. I especially wanted to demo some PHP5 specific features. The following example just creates a table with an autoincrementing primary key column 'id', inserts some values, fetches the last inserted id and finally, after selecting those values and outputs them using an iterator, drops the table again ..

I have received some questions why MDB2 does not support SQLite 3.x or why MDB2 does not provide PDO based drivers. That is actually one question as the only way to get SQLite 3.x support is to write a PDO based SQLite driver. Now this is a very important step MDB2 needs to take.

Today I finally released the next MDB2 version which finally promises a stable API. I am hoping to actually be able to release the first release labeled as "stable" before the end of the year. I have also pushed new releases for the two MySQL drivers, the PostGreSQL driver, the Oracle OCI8 driver, the SQLite 2.x driver and the Querysim driver. Furthermore I have released an updated version of MDB2_Schema.