There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply () below.
If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.
Join the Discussion. Help a fellow learner on their journey.
Ask or answer a question about this exercise by clicking reply () below!
You can also find further discussion and get answers to your questions over in Language Help.
Agree with a comment or answer? Like () to up-vote the contribution!
Its exactly what I predicted, you have an ambiguous column problem. The first name and last name field/column occur in both tables. So Sqlite can’t deal with it, here is some more information on the matter:
Just wanted to note, I came here to check the exact same thing as user ykstate - I completed the exercise and decided to try and replicate the same result with a JOIN for practice. I already thought the ambiguous columns were the issue but it’s a little strange that the example JOIN provided in the exercise DOES show ambiguous columns being used, caused me to second guess and think they don’t need specified.
If we’re using SQLite, then the example on the left should probably match the restrictions of the database engine we’re using. Fantastic course, just been tripped up a few times with similar issues
The exercise begins by saying that subqueries “can be nested inside of SELECT , INSERT , UPDATE , or DELETE statements.”… but then it immediately goes on to show an example of a subquery inside the WHERE … IN … clause? How is this possible if it said it can only be nested inside the clauses specified above?