Well there is a lot of back and forth about if PEAR should mandate PEAR_Error or PEAR_Exceptions or neither for new packages. This also relates to the question of PHP5 E_STRICT compliance which PEAR_Error obviously is not.

I decided to go with a bump of the minor version for the next release of MDB2 because there are a number significant changes and additions. One of the big changes is dropping array_key_exists() whereever possible. I kind of got bitten by isset() in the past a lot. Just stupid little mistakes. However I somehow felt more confident with replacing things with empty() calls. The same change was made across all drivers which were released as 1.1.0 versions (except for the Frontbase driver that needs a maintainer and the beta drivers for Oracle and Querysim).

Wouldn't it be cool if the open source RDBMS of the world got together to define a common protocol for debugging stored procedures? This opens up the possibility to share GUI tools and more importantly expertise in making it work to begin with.

In my own framework I have decided that there is plenty of structured data that I will never query on that I will just stick into the database as a serialized array. To make life easier I introduced a "serialize" datatype into the MDB2 datatype module of the WebBuilder2 framework. That way MDB2 will handle the (de-)serialization in your DML or SELECT SQL statements.

I am looking for a job starting this fall. By that time I should also hold a degree in computer science from the TU Berlin. My tasks on the job should be some how at least partially connected to open source and covering at a minimum 2 of the following 3 fields of expertise (in order of most preferred):