Just to add to what Tim said ;) -- you can't use dynamic query
cacheing if you use CFQUERYPARAMs So you need to make that decision up front before you implement either.
Just to throw my 2c in here as well -
I wouldn't have thought dynamic query caching would be a deal breaker - considering the number of ways CF allows you to set up your own caching models... application scope, wddx files etc etc etc, without having to rely of the cfquery/cache.
Personally - I would say - used stored procs for most things. Use cfquery for interesting dynamic sql, and if you want caching from those, spend 10 minutes and write your own.
If all you are using CFQUERYPARAM for is to protect your app from SQL injection then writing some validation is simpler than having to worry about managing the query cache. Dynamic querching is so *incredibly* simple to set up it seems a shame not to ;)
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
