DevShed continues their look at custom exception handling in PHP5 application with this third part of their series, a look at handling exceptions from MySQL calls.

Having already introduced you to the main subject of this article series, it's time to summarize the topics that were discussed in the last article, in case you haven't read it yet. In that particular tutorial I explained how to implement a fully-functional customized exception system with PHP 5, which came in handy for handling a number of specific exceptions thrown by a basic MySQL abstraction class.

They create a custom MySQL exception class that sits on top of their MySQL abstraction layer (and Result handling class) and catches exceptions thrown from sample queries.

On the Zend Developer Zone there's a new article that looks to answer the question in its title - "Why should I care what server my application is running on?" (by Eddo Rotman)

Imagine this - you develop an application on your machine and then, when you come to deploy it to the production server, all of a sudden, you encounter various errors and failures. Or maybe, when you decide to switch your hosting provider, your application stops behaving the way it should. How about this -... one day, out of the blue (well, out of your IT manager's whim) your application just misbehaves. Sounds familiar?

Times like can never be completely avoided (yes, there'll always be bugs) but you can take some steps to help prevent most of the major failing points. He points out some of the key configuration directives to watch out for, differences in some functions' responses based on the OS, and the differences in character sets between a unix-based and Windows based environment (like rn versus just n).

Some unfortunate news from Edin Kadribasic to be felt particularly by the Windows PHP users out there - the box that hosts the PECL packages for Windows has suffered a bit from a power failure.

The power failures are very rare in Denmark, but nonetheless this one managed to take out the build box. The website itself is not affected, but there are no updates for the time being.

The PECL4WIN project hosts a repository of PECL extensions precompiled for the Windows platform. The packaging and distribution system used by PECL is shared with its sister, PEAR.

UPDATE (11.15.2006) - The box is back up and working at 100% again (faulty memory was to blame). A new build has already been created.

PHP 5 has been presented as a revolution, a lot of new features have been added and a lot of projects have been made. But only a small group of hosters seem interested in supporting PHP 5 on their web servers. It is not so useful to have a beautiful programming language to use if we can't apply it to production environments.

We MUST use PHP 5 to help it growing until it become the standard...

PHP5 has seen a pretty slow adoption rate so far, but according to some statistics, its usage has been picking up lately - even among hosting providers.