I used to think that ColdFusion CFQueryParam's List and Null attributes required a "Yes" or "No" string. I always thought this was unusual, since so much of ColdFusion Yes/No attributes simply require a boolean value (ex. True, 1, 0, False). And, more than that, I could have sworn that I even tested this and was disappointed to see that true/false values actually threw ColdFusion exceptions!
But, apparently I read that somewhere and just accepted it like some ColdFusion Sheep in the herd. Thankfully, Elliott Sprehn has shown me the error of my ways. He told me that, like most of ColdFusion, the CFQueryParam Null and List attributes can, in fact, take standard boolean values:
- <cfquery name="qTest" datasource="#REQUEST.DSN.Source#">
- date_created =
- null="#NOT IsNumericDate( '2007/07/17' )#"
- id IN
When I run that, I get a ColdFusion query returned, not the formerly expected ColdFusion error. This is sweet-ass-sweet news! I always hated using the YesNoFormat() method as it adds so much noise to the already verbose ColdFusion CFQueryParam tag. This is gonna be so much nicer to use!
Looking For A New Job?
- Senior ColdFusion Software Engineer at CrowdTorch by Cvent
- Back-End Engineer - Node.js & Mongo at Interface Foundry
- Senior ColdFusion Web Developer at HD Web Studio
I love learning these little things that end up having a huge impact on the way I code.
Nice one Ben, for more reading: http://www.chapter31.com/2007/02/04/cfqueryparam-and-conditional-handling-of-nulls/
Thank god for Ben Nadel blog posts. I've spent the last 30 mins trying to work out why my query was throwing an error.
Looking at your example I realised I was missing the brackets around the list. School boy error.