I disagree with never using *. There are data access design patterns that play really well with *. So, one can easily blame the code that uses the result of the * query.
You do not know what to expect from the query, and your code becomes less easy to maintain because the fog of star query does not make it easy to perform changes (e.g. refactoring).
You will fetch fields that you do not care in case migrations added new fields on the table. Unoptimized bandwidth it is for sure.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I disagree with never using *. There are data access design patterns that play really well with *. So, one can easily blame the code that uses the result of the * query.
Star is bad for 2 reasons:
You do not know what to expect from the query, and your code becomes less easy to maintain because the fog of star query does not make it easy to perform changes (e.g. refactoring).
You will fetch fields that you do not care in case migrations added new fields on the table. Unoptimized bandwidth it is for sure.