I am curious to see what decisions your guys have made towards logging errors.
Currently, I need to store detailed information about errors in a database.
The scope of my engagement includes all web browsers. Therefore, I want to log
user web browser (#CGI.HTTP_USER_AGENT#) and also user ids
I am curious to see what decisions your guys have made
towards logging errors. Currently, I need to store detailed
information about errors in a database. The scope of my
engagement includes all web browsers. Therefore, I want to
log user web browser (#CGI.HTTP_USER_AGENT#) and also
:48 2007
Subject: RE: Logging Errors in Database
I am curious to see what decisions your guys have made
towards logging errors. Currently, I need to store detailed
information about errors in a database. The scope of my
engagement includes all web browsers. Therefore, I want to
log user
Therefore, I want to log user web browser (#CGI.HTTP_USER_AGENT#)
Not really useful. Differences in browser can cause script errors on
client side,
but are rarely responsible for errors on server.
Use CFERROR, collect anything you can, like session variables, etc. and
store it in a memo
First, wrapping your entire page with CFTRY is an awful idea. Don't do that.
Forgive me for being dense, but why is it an awful idea? System resources?
Granularity on code? Just sloppy or lazy?
Currently I have certain pages wrapped in a cftry and in the cfcatch I send
myself an email as
89107910. The opinions expressed within this
communication are not necessarily those expressed by Reed Exhibitions.
Visit our website at http://www.reedexpo.com
-Original Message-
From: Mik Muller
To: CF-Talk
Sent: Wed Feb 21 18:43:07 2007
Subject: RE: Logging Errors in Database
First
Forgive me for being dense, but why is it an awful idea?
System resources? Granularity on code? Just sloppy or lazy?
Currently I have certain pages wrapped in a cftry and in the
cfcatch I send myself an email as well as give the user a
polite apology for any inconvenience.
It's the
7 matches
Mail list logo
