Delete orders placed by users who are inactive.

Problem Statement

<p>Delete <code>orders</code> placed by <code>users</code> who are inactive.</p>

Examples

Input: users table: +----+-------+--------+ | id | name | active | +----+-------+--------+ | 1 | Alice | true | | 2 | Bob | false | +----+-------+--------+ orders table: +-----+---------+-------+ | id | user_id | total | +-----+---------+-------+ | 101 | 1 | 50 | | 102 | 2 | 75 | | 103 | 2 | 30 | +-----+---------+-------+

Output: +-----+---------+-------+ | id | user_id | total | +-----+---------+-------+ | 101 | 1 | 50 | +-----+---------+-------+

Explanation: The query retrieves the requested records satisfying all problem requirements.

Complexity

Time Complexity: -

Space Complexity: -

Hints

💡 Hint 1: Identify the filtering conditions needed to isolate the target rows from the table. 💡 Hint 2: Use appropriate operators: = for exact matches, LIKE for wildcard patterns, IN for sets, or BETWEEN for numeric/date ranges. 💡 Hint 3: Combine filters with AND/OR if multiple conditions exist: SELECT <cols> FROM <table> WHERE <condition>;

Editorial & Approach

Problem Overview & Intuition

To solve "DELETE with Subquery", we query the relational database engine using declarative SQL. The goal is to delete orders placed by users who are inactive. 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)

DELETE FROM orders WHERE user_id IN (SELECT id FROM users WHERE active = false); SELECT * FROM orders;

Complexity Analysis

Time Complexity O(N) full table scan or O(log N) if filtered column is indexed.

Space Complexity O(K) where K is the number of filtered rows returned.

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.

DELETE with Subquery

Medium

Delete orders placed by users who are inactive.

Example Scenarios

1Example 1

Input:

users table

id	name	active
1	Alice	true
2	Bob	false

orders table

id	user_id	total
101	1	50
102	2	75
103	2	30

Output:

id	user_id	total
101	1	50

Explanation:

The query retrieves the requested records satisfying all problem requirements.

SQL Editor

Loading Editor...

Query Results

Run a query to see results here.