Re: xml errors (was Re: [PHP-PEAR] DB error reporting and DB/ifx.php)
| From: | Chuck Hagenbuch | Date: | Wed, 28 Feb 2001 18:33:14 +0000 |
| Subject: | Re: xml errors (was Re: [PHP-PEAR] DB error reporting and DB/ifx.php) | ||
| Groups: | php.pear | ||
| Request: | Send a blank email to php-pear+get-1513@lists.php.net to get a copy of this message | ||
Quoting "Tomas V.V.Cox" <cox@idecnet.com>:
> Yes it is a great idea, IMHO perhaps a little bit complicated.
Yes; this is why I said "if you _have_ to return a structured string" (emphasis
added this time around). You should always be able to get a plaintext message
from an error for logging, which is why it'd be best not to have _any_ markup
in it at all - and html is a bad way to go if you need markup. And most of the
time you're not going to want to display db and other PEAR library errors
directly to the user - you want to log them somewhere or email them to someone,
etc. So markup should always be added later.
-chuck
--
Charles Hagenbuch, <chuck@horde.org>
"We have no fuel on board, plus or minus 8 kilograms." -A NASA scientist