>Vince - just out of curiousity, if I've got a bunch of code doing this:
>
><cfif foo eq "">
>
>and in some cases it's empty string and others it's null - would that
>code FAIL to wkr as expected under Bluedragon because null neq ""?
>
That code will work exactly as expected under BlueDragon 7.0. For backwards
compatibility, BD treats null database values as empty strings just as CF does;
but BD gives you the additional option of explicity checking for a null value.
So you can do this (I hope this formatting comes out right):
<cfif foo eq ""> <!--- database null or empty string --->
<cfif foo eq null >
<p>foo is a database null
<cfelse>
<p>foo is an empty string
</cfif>
</cfif>
I'm not sure you'd every write code exactly like that, but it illustrates the
point.
Vince
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Enterprise web applications, build robust, secure
scalable apps today - Try it now ColdFusion Today
ColdFusion 8 beta - Build next generation apps
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:290593
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
