Find users who have NO orders using NOT EXISTS.
Problem Statement
Examples
Input: users table: +----+---------+ | id | name | +----+---------+ | 1 | Alice | | 2 | Bob | | 3 | Charlie | +----+---------+ orders table: +-----+---------+-------+ | id | user_id | total | +-----+---------+-------+ | 101 | 1 | 50 | +-----+---------+-------+
Output: +----+---------+ | id | name | +----+---------+ | 2 | Bob | | 3 | Charlie | +----+---------+
Explanation: The query retrieves the requested records satisfying all problem requirements.
Complexity
Time Complexity: -
Space Complexity: -
Hints
Editorial & Approach
Problem Overview & Intuition
To solve "NOT EXISTS Subquery", we query the relational database engine using declarative SQL. The goal is to find users who have no orders using not exists. By formulating an optimal execution plan with appropriate projection and filtering, the database engine executes the query with minimal overhead.
Step-by-Step Approach
- Analyze Schema: Identify the target tables, necessary foreign keys, and expected output columns.
- Construct Filtering & Logic: Apply WHERE filtering to isolate the requested data.
- Format & Order: Ensure columns match the expected project schema in order.
Optimal Implementation (SQL)
SELECT * FROM users WHERE NOT EXISTS (SELECT 1 FROM orders WHERE orders.user_id = users.id);
Complexity Analysis
Key Considerations & Edge Cases
- Empty Tables: The query executes safely returning zero rows without syntax error.
- NULL Values: Columns containing NULL values are properly handled by standard ANSI SQL semantics.
- Case Sensitivity: String comparisons and keywords adhere to PostgreSQL/standard SQL rules.