as BobTheLantern said this issue is not reproducible with the code snippet you provided. you may have inadvertently modified the sample tests. feel free to reply here if you still encounter a problem.

It didn't for me. Could it be because of an interaction with Ruby?

That code passes all the tests, though.

What was the code that failed? Because IN definitely works here if you use it correctly.

You link the SQL IN operator page for help, but in the end I had to explicitly AVOID using 'IN' and do an '=' for it to work. The 'IN' was specifically the reason my code failed with your test, when (and I checked) code was correct. Frustrating.

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