I put it in the db so that it can be analyzed at a later date for quality, execs like to see fancy support stuff that really shows resolution, and in group dev/support environments errors can be assigned and solutions tracked.
As Robert touched on - we log to a file - (uing log4j) that way if the database is down we can still log errors (to file/email etc.) You can of course log to a csv and then management can open in excel and if they so desire create graphs - we use Jira so we can attach the log or a section to our issue tracker. HTH -- Kola BLOG:http://coolskool.blog-city.com/ SKYPE:kola.oyedeji "Time is an illusion. Lunchtime doubly so." - Douglas Adams You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
