When you use *, the database has to do a lookup to figure out what the actual column names are in the table, then do the actual select statement. If you explicitly tell it what column names (even if you want all of them), you eliminate that overhead.
Ryan, Terrence wrote: > I have a dumb question. Can someone point me to a definitive explanation > of why select * in SQL is bad? > > I've found this : http://www.adopenstatic.com/faq/selectstarisbad.asp > but I don't thing it effectively counters the argument "But I need all > of the columns in the table." > > Mind you, that I'm not looking for convincing for myself, rather I'm > doing a code review, and want to be have a stronger footing for saying: > "Get rid of the select *'s." > > Terrence Ryan > Senior Systems Programmer > Wharton Computing and Information Technology > E-mail: [EMAIL PROTECTED] > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:246099 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
