Table of Contents
Advertisement
CFML data types
ColdFusion MX preserves the case of a struct key, whereas ColdFusion 5 sets every struct key to
uppercase. However, you cannot use dot notation with different case to create more than one key.
For example, the following code produces one key, not two:
x.Foo = 1;
x.FOO = 2;
If you specify
x['Foo']
case for struct key names.
Template handlers
The Runtime service in Windows has been reimplemented in ColdFusion MX so that you can
specify a template handler in the ColdFusion MX Administrator (Settings page). (A template
handler is a template that executes when ColdFusion MX cannot find the CFM file specified in a
tag.) However, you must specify a template handler as a path that is relative to the
cfinclude
web root directory, such as \missing.cfm for the file web_root\missing.cfm. Do not use a full path.
Case in forms
Unlike ColdFusion 5, ColdFusion MX preserves the case of field names submitted by forms,
instead of forcing them to uppercase. Like ColdFusion 5, ColdFusion MX ignores case when
evaluating field names (for example,
However, you should change templates that use
Form.Fieldnames
Objects for date/time
ColdFusion MX no longer strips milliseconds off date/time objects; to do this, use the date
formatting functions.
Date pivot point for two-digit years
When ColdFusion processes a date that has does not include the century, ColdFusion determines
the century. To do this, ColdFusion compares the date to when it processes the date. With a few
exceptions, ColdFusion MX uses 20 as the date pivot point for calculating the century in a two-
digit year. ColdFusion 5 uses 29.
Note: The following locales use 28 as the date pivot point instead of 20: English (Australian), English
(New Zealand), German (Austrian), German (Standard), German (Swiss), Portuguese (Brazilian),
Portuguese (Standard), and Swedish. Macromedia has confirmed this inconsistency using the SUN
JRE version 1.4 and the IBM JRE version 1.3.0.
18
Chapter 1: Migrating Applications from ColdFusion 5
, ColdFusion MX preserves case. However, for best results, use consistent
#form.myfield#
variable, to use case-insensitive equivalents.
is the same as
#FORM.MYFIELD#
or
to search through the
Find
ListFind
).
Advertisement
Table of Contents
