Going off the recordcount would definately be less typing and easier on the
eyes.  :)

Yes when it comes out to null="Yes" then it is the same as if you typed in
WHERE ID IN (NULL)

On 3/8/06, Jim McAtee <[EMAIL PROTECTED]> wrote:
>
> I suppose this would work just as well, since recordid is a primary key:
>
> null="#YesNoFormat(not anotherquery.recordcount)#"
>
> I'm still not completely clear on how the null attribute is used.  If
> anotherquery comes back with a recordcount=0, then the cfsqlqueryparam
> attribute value would evaluate to something like:
>
> WHERE recordid IN
> (<cfqueryparam
> cfsqltype="cf_sql_varchar"
> value=""
> list="Yes"
> null="Yes">)
>
> Does this become the following in SQL, so that having null="Yes" just
> overrides the value parameter?
>
> WHERE recordid IN (NULL)
>
>
>


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:234758
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to