- 01Getting Started
- 02SELECT Statement Basics
- 03Filtering Rows with WHERE
- 04Sorting Results with ORDER BY
- 05Combining Tables with JOIN
- 06Aggregating Data with GROUP BY
- 07Fuzzy Matching with LIKE
- 08Modifying Data with INSERT, UPDATE, and DELETE
- 09Introduction to Subqueries
- 10Creating a VIEW
- 11Ranking Rows with Window Functions
- 12Understanding Transactions
- 13Writing Comments in SQL
- 14Logical Operators: AND, OR, NOT
- 15Working with NULL Values
- 16INNER JOIN vs. LEFT JOIN
- 17Filtering Aggregates with HAVING
- 18Removing Duplicates with DISTINCT
- 19Combining Results with UNION
- 20Conditional Values with CASE
- 21Checking Existence with EXISTS
- 22Changing Table Structure with ALTER TABLE
- 23Self Joins
- 24Speeding Up Searches with INDEX
- 25GROUP BY with Multiple Columns
- 26Pagination with LIMIT and OFFSET
- 27Pattern Matching with GLOB
- 28Date Calculations with the date() Function
- 29Joining Three Tables
- 30Matching Multiple Values with IN
- 31Derived Tables: Subqueries in FROM
- 32The Basics of TRIGGER
- 33Readable Queries with WITH (CTEs)
- 34UPSERT: Insert or Update in One Statement
- 35Combining MIN, MAX, and AVG
- 36Restricting Input with CHECK Constraints
- 37Auto-Numbering with AUTOINCREMENT
- 38Inspecting Query Plans with EXPLAIN QUERY PLAN
- 39ORDER BY with Multiple Columns
- 40Conditional Aggregation with CASE
- 41Removing Objects with DROP TABLE and DROP VIEW
- 42Combining Multiple CTEs
- 43Date Range Search with BETWEEN
- 44Finding What's Missing with NOT EXISTS
- 45Substituting NULL with COALESCE
- 46String Functions: UPPER, LENGTH, and SUBSTR
- 47Converting Types with CAST
- 48Merging Grouped Values with GROUP_CONCAT
- 49Enforcing Integrity with FOREIGN KEY
- 50Capstone: Build a Mini Library Management System
Self Joins
This lesson covers self joins — a technique for relating rows within a single table to each other. It's for anyone searching "SQL self join tutorial."
A self join joins a table to itself, useful for relationships within one table — like "senior and junior" or "manager and direct report."
The example references the employees table twice using aliases e and m, matching each employee's manager_id against the manager's own id, so it can display employee and manager names side by side. The key idea: giving a table two different aliases lets you reference it twice.
A common early mistake is not understanding why the same table needs two different aliases — since you're referencing the same table twice, each reference needs its own name to tell them apart. Without aliases, SQL can't tell which "copy" of the table a column belongs to. This pattern shows up whenever hierarchical relationships — an org chart, a family tree — are stored inside a single table, and once it clicks, it becomes a genuinely powerful technique.
💡 The SQL engine may take a few seconds to load the first time you run code.
