Calculate the total salary for IT and HR departments separately in one query.
Problem Statement
Examples
Input: employees table: +----+---------+------------+--------+ | id | name | department | salary | +----+---------+------------+--------+ | 1 | Alice | IT | 90000 | | 2 | Bob | HR | 60000 | | 3 | Charlie | IT | 120000 | | 4 | Dana | HR | 75000 | +----+---------+------------+--------+
Output: +----------+----------+ | it_total | hr_total | +----------+----------+ | 210000 | 135000 | +----------+----------+
Explanation: The records are grouped by category and the aggregate calculation is applied to produce the summary result.
Complexity
Time Complexity: -
Space Complexity: -
Hints
Editorial & Approach
Problem Overview & Intuition
To solve "CASE Inside Aggregate", we query the relational database engine using declarative SQL. The goal is to calculate the total salary for it and hr departments separately in one query. 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 SUM(CASE WHEN department = 'IT' THEN salary ELSE 0 END) AS it_total, SUM(CASE WHEN department = 'HR' THEN salary ELSE 0 END) AS hr_total 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.