> At my current 9-5 job my boss (the technical one) isn't sold on
> cfqueryparam, although he doesn't berate anyone for using it, he just
> turns his nose up... and although I hate to say it, we have worse
> problems in our application currently.

What reason would anyone have for turning their nose up at cfqueryparam? I 
can only think of one - that you can't cache the query using the built-in 
caching. But, there are still plenty of other ways to cache the data if you 
need it to be cached, and typically on a select that uses queryparams, you 
don't want to cache it anyway.

So, what's his rationale? 


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:205095
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

Reply via email to