It's still sloppy. For one thing, there's no way to tell what columns you're getting back unless you look at the table as well. I find it very rare that I need all columns from any table.
Any best practice document I've seen on SQL says to avoid SELECT *. On 7/20/05, Claude Schneegans <[EMAIL PROTECTED]> wrote: > >>You shouldn't ever use SELECT *. Name the columns you want. > > Well, ... except if you do need all columns, and SELECT * is standard in > SQL, especially for that purpose. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:212321 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
