Thanks to everyone on their help on this. I'll start looking at the suggested work-arounds.
Saturday On 13/1/05 7:03 pm, "Dave Watts" <[EMAIL PROTECTED]> wrote: >> It's not really a bug. Using <CFQUERYPARAM> with <CFQUERY> >> means that rather than a regular statement, CF is able to use >> prepared statements, so the execution plan (depending on the >> RDBMS you're working with) can be cached for extra execution speed. >> >> To cache with both, it's have to store the values passed into >> the CFQUERYPARAM tags, the prepared statement itself, and >> various other bits and pieces. They probably see it as being >> more trouble than it's worth. > > How hard could that be? What other various bits and pieces would they need > other than the query itself and the parameter values? > > I agree that it's not a bug, but it's certainly a poor implementation, just > like prior versions of CF couldn't support CFCOOKIE and CFLOCATION within > the same script. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > > Fig Leaf Software provides the highest caliber vendor-authorized > instruction at our training centers in Washington DC, Atlanta, > Chicago, Baltimore, Northern Virginia, or on-site at your location. > Visit http://training.figleaf.com/ for more information! > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:190421 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
