We're upgrading some of our applications from CF10 to CF2018.
On CF2018, we've unchecked 'Enable Null Support' in the ColdFusion Administrator, and we can see when we output the value of enableNullSupport
that it is set to NO. However, but we're still seeing behaviour which suggests that Nulls are enabled.
e.g. When we create an object with a property (eg FirstName) which is not initialised, the expression getFirstName() eq ""
, which previously was true, is now false
and IsNull(getFirstName())
is true
The article on Null support in ColdFusion 2018 says:
Now in your ColdFusion applications, you can assign null to a variable, as shown below:
<cfset price = null>
But if you try this line at https://cffiddle.org (with CF2018 selected), you get - Variable NULL is undefined.
It looks like the documentation around support for Null is misleading.