Querying Databases: WHERE and JOIN in SQL
1 of 4ICT · My World Quest — full scheme of work · pioneer
Querying Databases: WHERE and JOIN in SQL
For grown-ups
Companion summary
Imagine you could ask a giant library to find only the books written after 2010, by a specific author — that is exactly what WHERE does. Every app you use, from Spotify to school databases, runs queries like this behind the scenes to fetch just the right data. Here is a fact worth keeping: JOIN lets two separate tables talk to each other, like connecting a list of students to a list of grades using a shared ID column. When you finish, try writing a query that joins a "movies" table to a "directors" table and filters results with WHERE year >...
Warm-Up: Thinking About Tables
Warm-Up: Thinking About Tables
Imagine a school library keeps two lists. The first list has every student's name and their student ID number. The second list has every borrowed book and the student ID of the person who borrowed it. Could you figure out which student has which book? Of course — you match the ID numbers. That matching idea is exactly what SQL does for you automatically. Before you dive in, think about this: if you had a list of 10,000 students, how would you quickly find just the ones in Year 9? You need a way to filter. SQL gives you two powerful tools for exactly these tasks: WHERE and JOIN.
💭 Think about this
Can you think of two real-life lists of information that share a common piece of data — something that links them together?
What's next?
Next stop: France
A place you haven't discovered yet
A place you haven't discovered yet
Explore France →