NYCPHP Meetup

[David Mintz]

The bit about the infinite loop is nonsense, I now realize. The rest still
stands.

On Thu, 5 Feb 2004, David Mintz wrote:

> Even more interesting, if you call fetchRow with arguments
> DB_FETCHMODE_XXX and a $rownum, you go into an infinite loop. I didn't try
> to fix that.


---
David Mintz
http://davidmintz.org/

        "Anybody else got a problem with Webistics?" -- Sopranos 24:17

>From hans not junk at nyphp.com  Fri Feb  6 09:20:01 2004
Return-Path: <hans not junk at nyphp.com>
Received: from ehost011-1.exch011.intermedia.net (unknown [64.78.21.3])
	by virtu.nyphp.org (Postfix) with ESMTP id 62C0FA85FE
	for <talk at lists.nyphp.org>; Fri,  6 Feb 2004 09:20:01 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [nycphp-talk] Error Handling and Management
Date: Fri, 6 Feb 2004 06:19:57 -0800
Message-ID: <41EE526EC2D3C74286415780D3BA9F87772131 at ehost011-1.exch011.intermedia.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [nycphp-talk] Error Handling and Management
Thread-Index: AcPscVXroiEILrAgRPm8JAnuhgW+/gASppxQ
From: "Hans Zaunere" <hans not junk at nyphp.com>
To: "NYPHP Talk" <talk at lists.nyphp.org>
X-BeenThere: talk at lists.nyphp.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: NYPHP Talk <talk at lists.nyphp.org>
List-Id: NYPHP Talk  <talk.lists.nyphp.org>
List-Unsubscribe: <http://lists.nyphp.org/mailman/listinfo/talk>,
	<mailto:talk-request at lists.nyphp.org?subject=unsubscribe>
List-Archive: <http://lists.nyphp.org/pipermail/talk>
List-Post: <mailto:talk at lists.nyphp.org>
List-Help: <mailto:talk-request at lists.nyphp.org?subject=help>
List-Subscribe: <http://lists.nyphp.org/mailman/listinfo/talk>,
	<mailto:talk-request at lists.nyphp.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2004 14:20:01 -0000


> I was wondering how you guys handle your errors from project=20
> to project.  I consitently have an error handling class at=20
> the back of my mind which would handle all errors and report=20
> them correctly, whether it be to an external bug tracking app=20
> or customer support app, a log file, etc.  But the bridge=20
> between ideas and writing code for such a thing is of yet=20
> unbuilt.  Currently, I end up adding seperate error reporting=20
> per project and per class depending on the needs of the=20
> application.  So I was wondering what methods you use.

In most cases I take the easy/minimal approach.  That is, to show a
generic page with little information about the actual error, but then
use trigger_error() to log details.  This could easily be extended to
page/email someone, but having reports to a bug tracking app would take
a little more work (ie, custom handler for whatever app you're
interfacing with).

At one point, I was an avid user of setting a custom function to handle
errors, but I've shyed away from that lately.  Generally,
trigger_error() and then a redirect or include of an error page handles
all that I need, without the overhead of building a function (which must
always include the default php error handling) for each site.

H