Structured Query Language (DDL vs DML)

Target Audience: A Level Computer Science
The Learning Barrier: Transitioning from theoretical database design to writing functional SQL code. Learners often struggle to differentiate between structural commands (DDL) and data manipulation commands (DML), and they frequently hit a wall when trying to visualize how multiple tables link together through relational joins.
The Visual Strategy: I designed a highly relatable “Music Database” framework to contextualize the abstract code. By visually framing DDL as “building the container” and DML as “manipulating the data inside,” the syntax becomes intuitive rather than intimidating. The deck utilizes clean typography and color-blocking to break down complex queries step-by-step, making concepts like primary and foreign keys accessible.
The Outcome: Students are scaffolded from basic table creation all the way to writing complex SQL scripts, culminating in a final challenge where they successfully utilize multiple JOINs to query a relational playlist system.