Using a count makes that query completely useless. It can't be reused, nor does it return anything of relevance. Which means its sole purpose is to bring back a single number...
And no matter what you're calling, it's a hit on the DB, the web server memory and network traffic. To what extent depends on the query and coding style as well as the project in question. I'm not saying SELECT * is a better query, but I do believe it's smarter to roll multiple uses into a single result set. Cheers, Kevin -----Original Message----- From: Mark A Kruger [mailto:[EMAIL PROTECTED] Sent: August 30, 2005 10:38 AM To: CF-Talk Subject: RE: CF Test Kevin, This is not a pointless query <CFQUERY NAME="test" DATASOURCE="test"> SELECT Count(*) AS total FROM TestTable </CFQUERY> You would NOT want to select all the records in a table if all you wanted was the total. Otherwise you are bringing in the whole kit and caboodle and then just discarding the rows in favor of the meta data. It's a hit on the DB, the web server memory and network traffic - particularly for large recordsets. -Mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:216800 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
