FAQ: Subqueries - Non-Correlated Subqueries I

This community-built FAQ covers the “Non-Correlated Subqueries I” exercise from the lesson “Subqueries”.

Paths and Courses
This exercise can be found in the following Codecademy content:

SQL: Table Transformation

FAQs on the exercise Non-Correlated Subqueries I

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 (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 (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

Since these tables are not joined by an primary key, how does it identify commonalities?

4 Likes

no hints in the class?

i have the same question!

I have the same question too.

Because the subquery returns the airports codes which are the same as the codes in the flights origin columns, this is the commonality

5 Likes

Hi
If the nesting query is unrelated to main query, why do we have to use ‘code’ from the airports table to get the results …why can’t any other column be used ?

1 Like

Same question here! Why doesn’t it work when you replace ‘code’(from airports) with id (from airports)
both are unique?

I too have the same question - it should work with ID and code!

1 Like

Why are these producing different things? I don’t understand the usefulness of nesting queries over joining, but clearly the answer I get when I join is different so maybe there is a reason we’re supposed to use a nested query in this exercise:

select count(*) from flights join airports on airports.code=flights.origin where airports.elevation<2000;

select count(*) from flights where origin in (select code from airports where elevation<2000);

first produces 448 using join
second produces 438 using nesting (which they say is correct)

just checked results in excel, in the 448 there are 10 duplicates, ie flights wih id
402
2799
3077
4361
5505
10934
11808
12030
13712
14990

dunno why they get duplicated, since if you check on sql, their entries are unique, but somehow when you join the two tables these 10 ids get a double row.

would be great to know why