We know that in production code SELECT * is bad.

However, I will often write SELECT * in my SQL answers when

• The OP failed to include their SQL (so I've got nothing to copy and paste)
• The OP's question is really answered with the JOIN or WHERE
• There's no syntax in my answer like GROUP BY that SELECT * can easily conflict with. [A]

Recently someone thought an answer of mine would be improved if I removed the SELECT *. Obviously, I think it is acceptable to answer with SELECT * but I can't say why.

_{[A] I'm pretending that MySQL and its treatment of GROUP BY don't exist}

We know that in production code SELECT * is bad.

However, I will often write SELECT * in my SQL answers when

• The OP failed to include their SQL (so I've got nothing to copy and paste)
• The OP's question is really answered with the JOIN or WHERE
• There's no syntax in my answer like GROUP BY that SELECT * can easily conflict with. [A]

Recently someone thought an answer of mine would be improved if I removed the SELECT *. Obviously, I think it is acceptable to answer with SELECT * but I can't say why.

_{[A] I'm pretending that MySQL and its treatment of GROUP BY don't exist}

We know that in production code SELECT * is bad.

However, I will often write SELECT * in my SQL answers when

• The OP failed to include their SQL (so I've got nothing to copy and paste)
• The OP's question is really answered with the JOIN or WHERE
• There's no syntax in my answer like GROUP BY that SELECT * can easily conflict with. [A]

Recently someone thought an answer of mine would be improved if I removed the SELECT *. Obviously, I think it is acceptable to answer with SELECT * but I can't say why.

_{[A] I'm pretending the MySQL and its treatment of GROUP BY doesn't exist}

We know that in production code SELECT * is bad.

However, I will often write SELECT * in my SQL answers when

• The OP failed to include their SQL (so I've got nothing to copy and paste)
• The OP's question is really answered with the JOIN or WHERE
• There's no syntax in my answer like GROUP BY that SELECT * can easily conflict with. [A]

Recently someone thought an answer of mine would be improved if I removed the SELECT *. Obviously, I think it is acceptable to answer with SELECT * but I can't say why.

_{[A] I'm pretending that MySQL and its treatment of GROUP BY don't exist}

We know that in production code with SELECT * is bad.

However I often will write SELECT * this in my SQL answers when

• The OP failed to include their SQL (so I've got nothing to copy and paste)
• The OP's question is really answered in the JOIN or WHERE
• There's no syntax in my answer like GROUP BY that SELECT * can easily conflict with*.

Recently someone thought an answer of mine would be improved if I removed the SELECT *

Obviously I think its acceptable to answer with SELECT * but I can't say why.

_{* I'm pretending the MySQL and its treatment of GROUP BY doesn't exist}

We know that in production code SELECT * is bad.

However, I will often write SELECT * in my SQL answers when

• The OP failed to include their SQL (so I've got nothing to copy and paste)
• The OP's question is really answered with the JOIN or WHERE
• There's no syntax in my answer like GROUP BY that SELECT * can easily conflict with. [A]

Recently someone thought an answer of mine would be improved if I removed the SELECT *. Obviously, I think it is acceptable to answer with SELECT * but I can't say why.

_{[A] I'm pretending the MySQL and its treatment of GROUP BY doesn't exist}