StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I think your questions apply to error handling in general, so you may find some useful answers in language-agnostic questions.</p> <p>1. Soldarnal has answered question 1 and I would tend to agree - it's a lot of work to try catch every location where an error may occur such as database interaction, and better to have a global error handler which catches all errors and use try/catches in places where there is a highish likelyhood of an error occurring and you want execution to continue (generally if your site can't access your database it's a bit stuck).</p> <p>2. Regarding logging, <code>cflog</code> is the most robust as you can almost always log to a file unless there's severe problems with your server. <code>cfmail</code> is next - the server should queue any mails it can't send though there's more to go wrong. Next is <code>cfhttp</code> you can log your errors to an external site, though it will need to be up when the error is sent or you'll lose it. Finally you can log to a database, but again if that's down your stuck.</p> <p>You could use a combination e.g. log errors to a database, unless the database is unavailable then log to files and reinsert the errors into the database when it's back up.</p> <p>3. If you're tracking errors e.g. in a database or via an external service, you should be able to configure this to send you emails on the first error or <code>cfmail</code> will allow you to send mail on all errors. We use a custom built error handling script, but there may be some floating around the web.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload