SQL Basics Every Developer Should Know

Frameworks will happily generate SQL for you for years — until the day a query is slow, or wrong, or you need something the framework simply can't express. That's the day understanding SQL directly pays for itself.

SELECT is where you'll live

The vast majority of real SQL work is reading data, not writing it. Get comfortable with SELECT, WHERE for filtering, ORDER BY for sorting, and LIMIT for capping results — these four cover a large share of everyday queries.

SELECT name, email FROM users
WHERE created_at > '2026-01-01'
ORDER BY created_at DESC
LIMIT 20;

JOINs connect your tables

Relational databases split data across multiple tables to avoid duplication, and JOIN is how you recombine them for a query. An INNER JOIN returns only matching rows in both tables; a LEFT JOIN returns every row from the first table, filling in NULL where there's no match in the second — a distinction that trips up nearly everyone at first.

Indexes are why some queries are instant and others aren't

Without an index, the database scans every single row to find matches — fine for a hundred rows, painfully slow for ten million. An index on a frequently-filtered column lets the database jump directly to relevant rows instead. If a query is unexpectedly slow, checking whether the filtered column is indexed is often the first, highest-value thing to try.

Aggregate functions summarize, not list

COUNT, SUM, AVG, and GROUP BY turn many rows into a summary — "how many orders per customer," "average order value per month." Understanding that GROUP BY collapses rows sharing a value into one summarized row is the key mental model here; everything else follows from it.

Never trust raw string concatenation

Building a query by directly inserting user input into a string is how SQL injection vulnerabilities happen — a real, serious, and completely avoidable security risk. Always use parameterized queries or your database library's built-in escaping, never manual string concatenation with user-supplied values.

The takeaway

SELECT, JOIN, indexes, and aggregates cover most real-world SQL work. Learning them directly — rather than only through an ORM's abstraction — is what lets you diagnose the slow or wrong query instead of just hoping the framework handles it.