From my understanding of this exercise, when doing different tasks with SQL (querying, changing, creating) is each respective task supposed to end with a ';' or can there just be one at the end?

This was a good one.

the table is called users, not user. please do not open issues to ask for help.

for some reason age isn't registering as an element on my end? I don't know if it's a capitalization issue or something I'm doing wrong

Good warm-up or problem for beginners

Nice warm-up before tough kata's! Thanks!

The instructions do say that if you provide more than 3 answers you would be kicked out of trivia night for being too smart. :)

The second query is already written, the only thing you should do is complete the insert query.

INSERT --Your code here

SELECT * FROM participants;

I fail to see what's confusing there.

Bumping, because 3 years later it still hasn't been updated xD

There are 4, im not the only one who got bamboozled

There seems to actaully be 4 answers, and just showing the top 3 will work. I don't know if this is intended, but the description of the problem should be changed.

Mybe that's just me but from the way the exercise is worded, I assumed it was expected to write a query that would ONLY insert the new row IF the participant was age 21 or older.
Another way to understand it would be that at any attempt that you try to add a particpant younger than 21 to the table, it would change the 'attending' column to False.

Both ways seem too hard for a Kyu 8 level, but well... the wording should really be reconsidered.

For my fellow strugglers: You need to first simply insert your row and then just print the table with the age-condition.

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.

walk in the park