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

Read this: https://www.prisma.io/dataguide/postgresql/short-guides/quoting-rules#:~:text=In%20PostgreSQL%2C%20double%20quotes%20(like,specifically%20marked%20beginning%20and%20end.

In SQLite 3.2.8 you could use one or the other.

Why it doesn't accept double quotes?

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.

Good question. Not necessary, not sure why I had them included.

you are correct, i didn't need outer scoped variable.

whatever what? 😊

no, what did they change?

whatever man! :)

Why the static int?
Could just have declared the int in the method. ^^

Like:

int totalOnBus = 0;

Try to do the hard work with maths. I got it working in < 1ms for larger numbers than the solution asks. You don't want to be looping through every number between 1 and the given number.