Jump to content

Recommended Posts

  • 1 month later...

Personally, I like to collect some or all this data:

  • datetime when the error occurred
  • filename where the error occurred
  • class and function where the error occurred
  • category of the error (database, bad input, logic, etc)
  • if this occurred in Pear::MDB2, then record the Pear error message
  • error level (critical, low, etc)

 

I put all those into an object and that gets passed to an error handling object that looks at the error level and decides if it should send an email to me, log it into a file, or insert the error message into a database.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.