If I am not wrong, this is the best practice because of the following reasons:

1. It fetches only the required columns, reducing the amount of data transferred. By doing this, it also limits the possible exposure of sensitive data.
2. SQL keywords should be consistently capitalized to improve readability.

Maybe for this particular case, using '*' after the keyword 'SELECT' could lead to the same result, but I think it is good to develop the habit of just fetching the required columns by using their names and thus avoiding the possible fetching of unnecessary or sensible data.

Not the Best Practices definatly

In theory, yes. Bust in many cases the time saved by using a wildcard is more important. Plus, you can limit your sample to, let's say, 100 rows and not worry about how many columns you have there anymore.

did't know I could use ::text

The next part of the sentence is what makes it confusing. Although it does make interesting reading, it's harder to read. Please delete "containing each character's high school, their civilian name and the cat who introduced them to their magical crime-fighting destiny."

nice

I think I covered that here - "Return a results table - sailor_senshi, real_name, cat and school" - does it need to be clearer than that?

Looks like it does still rename and pass without AS - so, should I keep the AS requirement because it's best practise, or leave it out because ultimately people might go for succinct solutions and omit stuff they feel is optional...

edit: removed requirement.

Good luck renaming your columns without using AS at all!

Instructions are too confusing, you need to state the columns you want returned. Also you shouldn't specify that the query should contain 'AS' since this isn't required.

what is fixed? I do not see the comment since it is hidden.