With cfparam, you have built-in type checking. It also can help to avoid loads of cfif statements because you KNOW the variable is there, you just need to check it's value.
<!----------------//------ andy matthews web developer ICGLink, Inc. [EMAIL PROTECTED] 615.370.1530 x737 --------------//---------> -----Original Message----- From: Duncan [mailto:[EMAIL PROTECTED] Sent: Monday, February 13, 2006 4:25 PM To: CF-Talk Subject: cfquery param vs <cfif + N What is the difference of doing this: <cfif getClient.saveAsUnicode eq 1>N</cfif>'#address#', over this: <cfqueryparam value="#address#" cfsqltype="cf_sql_varchar"> Is there a performance gain? How does CF handle this differently? Does cfqueryparam behave the same in 5,6 and 7? Does SQL do anything differently? Any general points would also be grateful. I am just trying to understand the differences better - I know everyone goes around saying you must use cfqueryparam beacuse its better, security etc etc. So I am just trying to validate this a bit. -- Duncan I Loxton [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232189 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
