Comments on: cfqueryparam and conditional handling of NULL’s http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/ development in a land far far away... Wed, 15 Oct 2008 23:57:05 +0000 http://wordpress.org/?v=abc By: jDowdle.com » Blog Archive » cfqueryparam, NULLs and Lists http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-71833 jDowdle.com » Blog Archive » cfqueryparam, NULLs and Lists Wed, 17 Sep 2008 16:39:19 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-71833 [...] Links: cfqueryparam and conditional handling of NULL’s [...] [...] Links: cfqueryparam and conditional handling of NULL’s [...]

]]> By: Michael Sharman http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-55686 Michael Sharman Sat, 21 Jun 2008 01:20:48 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-55686 @Eric - This would indeed work for varchars, not sure what went wrong for you. Do you have a code sample? For radio buttons you could replace len(trim()) with isDefined("myRadioButton") Hope that helps. @Eric - This would indeed work for varchars, not sure what went wrong for you. Do you have a code sample?

For radio buttons you could replace len(trim()) with isDefined(”myRadioButton”)

Hope that helps.

]]> By: Eric Smith http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-55635 Eric Smith Fri, 20 Jun 2008 19:22:16 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-55635 You also need to mention that this is not for radio boxes. Spent a good deal of time finding this out the hard way. Thanks, Eric You also need to mention that this is not for radio boxes. Spent a good deal of time finding this out the hard way.

Thanks,
Eric

]]> By: Eric Smith http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-55595 Eric Smith Fri, 20 Jun 2008 14:44:20 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-55595 Will this work for a varchar field also? I tried using your example and just replaced your field name and the data type and it's not working. Thanks, Eric Will this work for a varchar field also? I tried using your example and just replaced your field name and the data type and it’s not working.

Thanks,
Eric

]]> By: Michael Sharman http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-41454 Michael Sharman Thu, 13 Mar 2008 03:22:55 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-41454 @Tracy - Yep, the last example in the post details that. There was a problem with the syntax highlighter I was using so I don't think it was displaying correctly. I've removed the highlighter for the last example and just left it bold. Thanks @Tracy - Yep, the last example in the post details that.

There was a problem with the syntax highlighter I was using so I don’t think it was displaying correctly.

I’ve removed the highlighter for the last example and just left it bold.

Thanks

]]> By: Tracy Logan http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-41420 Tracy Logan Wed, 12 Mar 2008 16:34:42 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-41420 Note that (at least with CF8), there's no need for using YesNoFormat() -- like all other CF tag attributes that expect a boolean value, all the usual CF booleans will suffice (0/1, no/yes, true/false). So a simple ...null="#NOT structKeyExists(arguments, 'age')#"... will do the trick. I would expect this to be true of all CF versions, but only have CF8 ready to hand. Note that (at least with CF8), there’s no need for using YesNoFormat() — like all other CF tag attributes that expect a boolean value, all the usual CF booleans will suffice (0/1, no/yes, true/false). So a simple …null=”#NOT structKeyExists(arguments, ‘age’)#”… will do the trick. I would expect this to be true of all CF versions, but only have CF8 ready to hand.

]]> By: Adam Ness http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-2027 Adam Ness Thu, 08 Feb 2007 01:53:05 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-2027 I tend to use <cfqueryparam ..... null="#trim(iFormElement) eq ''#">, which I think compiles to the same thing on the backend. I ran some fairly extensive speed comparison tests between eq "" and not(len()) a while back and came up with the same numbers, though that was on CFMX 6.1, things may have changed in 7 I tend to use
<cfqueryparam ….. null=”#trim(iFormElement) eq ”#”>, which I think compiles to the same thing on the backend. I ran some fairly extensive speed comparison tests between eq “” and not(len()) a while back and came up with the same numbers, though that was on CFMX 6.1, things may have changed in 7

]]> By: Adam Ness http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-2026 Adam Ness Thu, 08 Feb 2007 01:52:15 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-2026 I tend to use , which I think compiles to the same thing on the backend. I ran some fairly extensive speed comparison tests between eq "" and not(len()) a while back and came up with the same numbers, though that was on CFMX 6.1, things may have changed in 7 I tend to use
, which I think compiles to the same thing on the backend. I ran some fairly extensive speed comparison tests between eq “” and not(len()) a while back and came up with the same numbers, though that was on CFMX 6.1, things may have changed in 7

]]> By: Julian Halliwell http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-1913 Julian Halliwell Mon, 05 Feb 2007 19:43:12 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-1913 Nice explanation Michael. I've been using the YesNoFormat trick for a while but the double negatives have always bothered me. For strings (and as Peter says it's normally strings) I've recently started using a simple "isEmptyString" UDF to make my cfqueryparams more readable. Nice explanation Michael. I’ve been using the YesNoFormat trick for a while but the double negatives have always bothered me. For strings (and as Peter says it’s normally strings) I’ve recently started using a simple “isEmptyString” UDF to make my cfqueryparams more readable.

]]> By: Peter Bell http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-1853 Peter Bell Sun, 04 Feb 2007 17:11:28 +0000 http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/#comment-1853 That is nice approach to using the null - quite cool! One other approach to handling this for integers is to RegEx your string to remove all non-numerics. If you really think it through, the benefits of cfqueryparam are primarily for strings as it stops you having to try to parse a string to remove any possible variant of delete table (or whatever injection required). For bits, dates, integers, floats and the like, a simple regex transformation and/or validation in your code is (to my mind) simpler. Just my 2c! That is nice approach to using the null - quite cool! One other approach to handling this for integers is to RegEx your string to remove all non-numerics.

If you really think it through, the benefits of cfqueryparam are primarily for strings as it stops you having to try to parse a string to remove any possible variant of delete table (or whatever injection required). For bits, dates, integers, floats and the like, a simple regex transformation and/or validation in your code is (to my mind) simpler.

Just my 2c!

]]>