Specifications
CFML tags and attributes 11
cfprocparam
Changed The maxrows attribute is obsolete in ColdFusion MX. If
you have ref cursors in packages or stored procedures,
use cfprocresult instead. This causes Datadirect
JDBC to place the Oracle ref cursors into a result set.
(Note: you cannot use this method with the Oracle
ThinClient JDBC drivers.)
See cfprocparam
and cfprocresult in
CFML Reference
.
The cfprocparam tag ignores the dbvarname attribute
for all drivers. (ColdFusion 5 used it for Sybase, Oracle,
and Informix native drivers.) ColdFusion MX is a JDBC
client which does not support named parameter passing
like the Sybase ctlib and Oracle oci libraries.
cfquery
Changed The cfquery tag disallows SQL reserved words as
variable or column names in a Query of Queries, unless
they are escaped. To escape a reserved word, enclose it
in brackets; for example: select [COUNT] from
myTable or
select [FROM] from popQuery
See cfquery in
CFML Reference
.
Measures the timeout value in seconds, instead of
milliseconds as in ColdFusion 5. You must convert each
timeout value from milliseconds to seconds.
cfquery,
cfinsert,
cfgridupdate,
cfupdate,
cfstoredproc
Changed In ColdFusion MX, all values of the dbtype attribute are
deprecated except for dbtype="query", and
dbtype="dynamic" is obsolete.
This is because ColdFusion MX uses the data source
services provided by the underlying J2EE server, which
provides better scaling and connection support in most
cases. However, it only supports passing in the
username and password, which is insufficient to define a
data source. ColdFusion 5 can do this because it uses
Open Database Connectivity (ODBC) to establish a
database connection.
To work around this, define a data source to connect to
the database.
See cfquery,
cfinsert,
cfgridupdate,
cfupdate, and
cfstoredproc in
CFML Reference
, and
the “Data Source
Management” chapter
in
Administering
ColdFusion MX
.
The dbserver, dbname, connectstring, provider,
and providerdsn attributes are obsolete in ColdFusion
MX.
cfregistry
Deprecated
for UNIX
Registry operations will be obsolete in later UNIX
versions of ColdFusion MX.
See “Using cfregistry
in ColdFusion MX” on
page 28.
Changed In Windows, you should not use cfregistry to read
ColdFusion server settings—such as the mail root and
information about Verity collections and scheduled
tasks—because much of this information is no longer
stored in the registry, or it is stored in a different location
in the registry. The ColdFusion-related values that are
stored in the registry are subject to change.
Tag Status Compatibility issue
For more
information