Pivot total sales per department into columns (HR, IT, Sales).
Problem Statement
Examples
Input: sales table: +------------+--------+ | department | amount | +------------+--------+ | HR | 100 | | IT | 200 | | IT | 150 | | Sales | 300 | +------------+--------+
Output: +----------+----------+-------------+ | hr_sales | it_sales | sales_sales | +----------+----------+-------------+ | 100 | 350 | 300 | +----------+----------+-------------+
Explanation: The query retrieves the requested records satisfying all problem requirements.
Complexity
Time Complexity: -
Space Complexity: -
Hints
Editorial & Approach
Problem Overview & Intuition
To solve "Pivot Data using CASE", we query the relational database engine using declarative SQL. The goal is to pivot total sales per department into columns (hr, it, sales). 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 = 'HR' THEN amount ELSE 0 END) AS hr_sales, SUM(CASE WHEN department = 'IT' THEN amount ELSE 0 END) AS it_sales, SUM(CASE WHEN department = 'Sales' THEN amount ELSE 0 END) AS sales_sales FROM sales;
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.