On 7/5/05, Dave Watts <[EMAIL PROTECTED]> wrote: > In this particular case, viewed alone, there's no reason to do this. > However, you might have another query somewhere else like this: > > select emp.name, emp.salary > from emp > where emp.id = 325 > > I think this would generally result in two execution plans, which would > essentially be the same. In that case, why have the database do the work of > recalculating the second execution plan?
You're right. Maybe the example SQL I gave was not a good one. The bottom line is, whenever you have a "static SQL" that does not change across your application, using bind variables in that SQL (through cfqueryparam) is not necessary. That's my understanding. -- Eddie. http://awads.net/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:211216 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
