Installation guide
hold the result set. The following code running on BlueDragon 6.1 returns the result set
in a query variable named "
myResults":
<cfstoredproc proc="myProc" datasource="dsn">
<cfprocparam type="IN" value="#inValue#">
<cfprocparam type="OUT"
cfsqltype="CF_SQL_REFCURSOR"
variable="myResults">
</cfstoredproc>
In CF5, you're required to specify a "dummy" OUT parameter and then use CFPROCRESULT
to create a variable to hold the actual result set. The following code running on CF5
returns the result set in a query variable named "
myResults":
<cfstoredproc proc="myProc" datasource="dsn">
<cfprocparam type="IN" value="#inValue#">
<cfprocparam type="OUT"
cfsqltype="CF_SQL_REFCURSOR"
variable="dummy">
<cfprocresult name="myResults" resultset="1">
</cfstoredproc>
CFMX differs from CF5 in that you don't use the CFPROCPARAM tag to specify a dummy
OUT variable, but only specify the CFPROCRESULT tag to access the results. The following
code running on CFMX returns the result set in a query variable named "
myResults":
<cfstoredproc proc="myProc" datasource="dsn">
<cfprocparam type="IN" value="#inValue#">
<cfprocresult name="myResults" resultset="1">
</cfstoredproc>
4.3.28 CFTEXTINPUT
ColdFusion allows the
BGCOLOR and TEXTCOLOR attributes to be specified as hex values in
the form “
#nnnnnn”, although the documentation indicates the pound sign should be
escaped, as in “
##nnnnnn”. BlueDragon follows the documented approach and requires
that the pound sign be escaped. As a work-around, if you used the undocumented single
pound sign, changing it to use two will still be compatible with ColdFusion.
4.3.29 CFTREE
BlueDragon does not support the following optional
CFTREE attributes:
completePath
delimiter
onValidate
4.3.30 CFTREEITEM
BlueDragon does not support the following optional
CFTREEITEM attributes:
img
imgOpen
BlueDragon 6.1 CFML Compatibility and Reference Guide 14