> Except, since Coldfusion is declaring the bind variables
> and passing them in, and there is no "null" in coldfusion,
> just "empty string", I can see where that might be a problem.
> Because CF tries to pass an
> empty string into a bind variable that's expecting an int.
It is only an issue when null="false". When the "null" attribute is set to
true, the cfqueryparam "value" is ignored and a special sql type representing
NULL is sent to the database instead. So this is perfectly valid
WHERE IntColumn IN
(
<cfqueryparam value="" null="true" cfsqltype="cf_sql_integer" list="true">
)
So as Carl mentioned, they need to modify their code so null="true" when the
value is an empty string "". Not just when the variable does not exist.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:336212
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
