Right, but if that table grows and columns are added, the overhead on your query will grow. Having a small table makes it even easier to define the columns in your select list. And, if you have any dynamic code that relies on your column list it will likely break if you end up adding columns to the table. Or if you have to hand off your code to another developer they can't simply look at your query statement and glean what's being returned without having access to the db or without dumping the query.columnList. There's just so many reasons why defining your column list is a good idea, and none where not defining it is.
Not trying to preach, but this bit of "convenience" is just so unnecessary and has such potential for problems that it's not even worth considering in my opinion. It's just such a horrible habit. Anyway, as you were. :) </soapbox> On Tue, Jun 21, 2011 at 5:15 PM, Jenny Gavin-Wear < jenn...@fasttrackonline.co.uk> wrote: > > I was waiting for a comment on that. > > It's a very small table :) > > >>-----Original Message----- > >>From: Michael Grant [mailto:mgr...@modus.bz] > >>Sent: 21 June 2011 19:46 > >>To: cf-talk > >>Subject: Re: SQL Query Problem > >> > >> > >> > >>Off topic, but the "Select *" made me shudder. > >> > >> > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:345510 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
