
383
DEVELOPING
COLDFUSION 9 APPLICATIONS
Developing CFML Applications
Las
t
upda
te
d 8/5/2010
Stored Procedures
The stored procedures section displays information about the results of using the
cfstoredproc
tag to execute a
stored procedure in a database management system.
The output displays the following information:
•
Stored procedure name
•
Data source name
•
Query execution time
•
Page on which the query is located.
•
The time when the query was made.
•
A table displaying the procedure parameters sent and received, as specified in the
cfprocparam
tags, including the
ctype
,
CFSQLType
,
value
,
variable
, and
dbVarName
attributes. The
variable
information for OUT and INOUT
parameters includes the returned value.
•
A table listing the procedure result sets returned, as specified in the
cfprocresult
tag.
Exceptions
In the Administrator, when Exception Information is selected on the Debugging Settings page, the debugging output
includes a list of all ColdFusion exceptions raised in processing the application page.
The exception information includes information about any application exceptions that are caught and handled by
your application code or by ColdFusion.
Exceptions represent events that disrupt the normal flow of an application. You should catch and, whenever possible,
recover from foreseeable exceptions in your application, as described in “
Handling Errors
” on page 275. However, you
might also want to be alerted to caught exceptions when you are debugging your application. For example, if a file is
missing, your application can catch the
cffile
exception and use a backup or default file instead. If you enable
exception information in the debugging output, you can immediately see when this happens.
Trace points
In the Administrator, when Tracing Information is selected on the Debugging Settings page, the debugging output
includes the results of all
cftrace
tags, including all tags that display their results inline. Therefore, the debugging
output contains a historical record of all trace points encountered in processing the request.
For more information on using the
cftrace
tag, see “
Using the cftrace tag to trace execution
” on page 385.
Scope variables
In the Administrator, when the Variables option and one or more variable scopes are selected on the Debugging
Settings page, the debugging output displays the values of all variables in the selected scopes. The debugging output
displays the values that result after all processing of the current page.
By displaying selected scope variables you can determine the effects of processing on persistent scope variables, such
as application variables. This can help you locate problems that do not generate exceptions.
The Form, URL, and CGI scopes are useful for inspecting the state of a request. They let you inspect parameters that
affect page behavior, as follows:
URL variables
Identify the HTTP request parameters.
Form variables
Identify the form fields posted to an action page.
CGI variables
Provide a view of the server environment following the request.