Re: MySQL class. Thoughts?

I prefer to deal with the issues locally, or have a documented behaviour with return values and error details available, much like most of PHP extensions/internals. try/catch ends up with weird code organization, imho, especially when you can only really handle some exceptions. For real fun, one API layer will catch all the lower exceptions, then wrap them in a generic exception, and you have to string parse $e->getMessage() to figure out what to *do*. [shudder]