it's nice when mine matches the top answer

same sol

And mine! ;)

An anti-pattern can create an error later on or cause technical debt. Which is why one should only select the columns that they need in a query. Where I disagree with this statment of using SELECT * as an anti-pattern in this instence is that Kata asked to "select all" which is literally what SELECT * means.

Good!!!!

this won't be changed now after 2,000+ completions 🤷

We have to SELECT all the rows (*) From Table_name
Put condition (WHERE....)
For shorting We use 'ORDER BY' Clause
For Descending order we have write 'DESC', By defaul it get in Ascending orer.

What is meant by this, "anti-pattern"?

It ensures case-insensitivity:

"Alligator" != "alligator"

Forcing the animal to lower case means it will always match properly.

identical to my solution ! :D

Good one man!

I am getting this error:

PG::UndefinedColumn: ERROR: column "created_at" does not exist

Yet your event's table schema description states that column

"events" Table Schema:
id
name (String)
created_at (DateTime)
description (String)

You have a point there yourself!

You definitely have a point. But invalidating 160 solutions on a 2 year old 1kyu kata may not be the best course of action.