That dumb coworker who worked with SELECT *; statements exclusively.

Seriously? Wow

Just so you guys can chill - he was fired after the first month. At that time it was me who had to clean up his mess though.

@csessh It is not and it is hard to understand my rant if you've never worked with sql. :)

I wouldnt lose sleep over it if the table has less than 1000 records and wont grow exponentially (eg an administrators table). Definitely not ideal for optimisation though.

That's some poor SQL

select * from * where * = *; i seriously have a co-worker that selected * from a table which is (legacy table) over 4 gb. everything broke. seriously. the whole of our client base lost evrything for an hour #poordesignchoicesmuch

@joetj don't forget ORDER *; (I know not valid but I'm keeping with the theme)

my coworker once put a 52 column table in a combo box