Categorize employees by salary: "High" for > 100000, "Medium" for > 60000, otherwise "Low".
Problem Statement
Examples
Input: employees table: +----+---------+--------+ | id | name | salary | +----+---------+--------+ | 1 | Alice | 120000 | | 2 | Bob | 75000 | | 3 | Charlie | 50000 | | 4 | Dana | 90000 | +----+---------+--------+
Output: +---------+--------+-------------+ | name | salary | salary_band | +---------+--------+-------------+ | Alice | 120000 | High | | Bob | 75000 | Medium | | Charlie | 50000 | Low | | Dana | 90000 | Medium | +---------+--------+-------------+
Explanation: The query retrieves the requested records satisfying all problem requirements.
Complexity
Time Complexity: -
Space Complexity: -
Hints
Editorial & Approach
Problem Overview & Intuition
To solve "Searched CASE (Multiple WHEN)", we query the relational database engine using declarative SQL. The goal is to categorize employees by salary: "high" for > 100000, "medium" for > 60000, otherwise "low". 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 row projections to isolate the requested data.
- Format & Order: Ensure columns match the expected project schema in order.
Optimal Implementation (SQL)
SELECT name, salary, CASE WHEN salary > 100000 THEN 'High' WHEN salary > 60000 THEN 'Medium' ELSE 'Low' END AS salary_band FROM employees;
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.