Lucee 4.5.2 cfparam null value error with full null support
With cfparam and the full null support (non default behaviour) there is a dodgy impact:
Suppose qryDB has a null valued column, and you set a variable to that null value
<cfparam name="myVar" default="#qryDB.nullValueColumn#">
This throws an error, same as would happen in this instance;
<cfparam name="myVar">
Though the later appears to be inconsistently present in Adobe ColdFusion also;
http://blog.adamcameron.me/2013/04/coldfusion-bugs-id-like-to-see-dealt.html
Suppose qryDB has a null valued column, and you set a variable to that null value
<cfparam name="myVar" default="#qryDB.nullValueColumn#">
This throws an error, same as would happen in this instance;
<cfparam name="myVar">
Though the later appears to be inconsistently present in Adobe ColdFusion also;
http://blog.adamcameron.me/2013/04/coldfusion-bugs-id-like-to-see-dealt.html
Comments
Post a Comment