I just spammed 10 new releases into the wild. For LiveUser these were just minor updates. The MDB2 and MDB2_Schema releases were much more major albeit not as far fetching as I originally hoped. However these releases should work better than the previous and most importantly should not emit errors in PHP 4.4.x and 5.0.5. I also noted the key todo items in each of the MDB2 package's in the changelog.

I have started to get into an MDB2 hacking frenzy. This is not necessarily a good idea as I have tons of writing to do. Oh well I guess I will have to get into a writing frenzy soon as well.

Last week I made the promise to make another round of MDB2 and MDB2_Schema releases by the end of next week. Appearently more and more projects are picking up MDB2_Schema like Jaws and Chiara_PEAR_Server. So I have a few more days to fix things up. I am a bit sick after 3 days of outdoor mixed championships. My frisbee team ended up second. We lost the finals 14:12 after leading 10:12 (game was played til 13, cap 2, with a maximum of 15). However it was still quite exciting to play at such a high competitive level for me. We have multiple teams in Berlin and so I am a member of two teams, but I have mostly played with the one that plays 2nd league level. So usually I am one of the guys who handles the disc alot and makes alot of catches. But in this top level team I was solely focused on defense and I even managed to force a number of turnovers onto our opponents in the finals.

A while ago I implemented native prepared statements into the MDB2 mysqli driver. However I was never able to get LOB support to work in the execute method. I almost forget about this and only stumbled over this issue again while testing a new portability fetch mode that fixes the issue of sqlite returning table qualifiers in associative fetches unlike most other DBMS extensions in PHP. Maybe someone has experience here and/or is motivated to fix the problem.

I am always suprised at the bitterness of flamewars on open source mailinglists, IRC chats and blog posts. Often these flamewars spring from cultural differences, language barriers, little mistakes or oversights. Sometimes they also spring from the assumption that someone does not know the given system well enough or did not bother to read the documentation. Rarely do they spring from proper technical arguments and even then it seems odd to start using the rather aggressive tone which result in the flamewar label.