If you actually need every one of the columns in a single (or multiple)
row(s) then select * saves time. Isn't that we all try to do, save ourselves
time? Why not in this case?

<!----------------//------
andy matthews
web developer
certified advanced coldfusion programmer
ICGLink, Inc.
[EMAIL PROTECTED]
615.370.1530 x737
--------------//--------->

-----Original Message-----
From: Ryan, Terrence [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 11, 2006 10:05 AM
To: CF-Talk
Subject: Select * in SQL


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:246100
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to