Lol-- Splitting hairs on technical verbiage are we? Call it what you want, but I prefer to see my database as a sort of "server-superhero" who's spider sense tingles when I make more than "6 modifications to a temporary table" inside my stored procs.
Hmm, all this talk of procs, prepared statements, and caching reminds me of the debate over whether stored procs are better than cfqeries using cfqueryparam. My last DBA swore up and down that stored procs would ALWAYS perform better than ColdFusion's "inline queries". I never really knew enough to debate definitively on the subject with him, but always assumed there wasn't really much of a difference. Of course, there seems to be articles supporting both points of view out there. ~Brad -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 8:33 PM To: CF-Talk Subject: RE: Is cfqueryparam worth it? > Given that the DB is likely to recompile the code if it > senses that the current plan may not be optimal I assumed you > were pointing out that there would be overhead in the > generation of the new plan. There are a set of specific things that will cause the database to recompile the plan. It's not really a matter of "sensing that the current plan may not be optimal". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:286012 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
