In my experience, it only slowed things down. Now, YMMV, but I've noticed that the more cfqueryparams you have in your query, the slower it will run. Although theoretically the sql engine should have an easier time caching an execution plan for your query, the only reason I have found to use cfqueryparams is for security. And even then, I have not seen a way to create sql injection attacks with CF, unless you're doing something stupid, like preserveSingleQuotes().
Can anyone give a good argument for using cfqueryparam? Russ > -----Original Message----- > From: Mary Jo Sminkey [mailto:[EMAIL PROTECTED] > Sent: Monday, January 08, 2007 1:26 PM > To: CF-Talk > Subject: Re: Cfqueryparam on ALL values or just user definable ones? > > >Could you explain a little please? It would seem to me that using an > extra > >function or tag would increase processing time. > > The limiting factor here is not the CF code, it's the database processing > time. Using binding variables will generally speed that up. > > --- Mary Jo > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:265987 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
