> 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! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Purchase RoboHelp from House of Fusion, a Macromedia Authorized Affiliate and support the CF community. http://www.houseoffusion.com/banners/view.cfm?bannerid=59 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:190291 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
