1. Database Programming Sections 6 –Subqueries, Single Row Subqueries, Multiple-row Subqueries, Correlated Subqueries

2. Subqueries  Subqueries don’t use the following operators: BETWEEN...AND, IN, LIKE, or IS NOT NULL  If the above operators they will execute if and only if they return only one row  Null value returned then no rows displayed  If more than one value returned, error will occur Marge Hohly2

3. 3 SUBQUERY  SELECT statement that is embedded in a clause of another SELECT statement  Can be placed in the WHERE clause, the HAVING clause, and the FROM clause.  The inner query is called the “subquery”  Subquery executes first and its output is used to complete the query condition for the main or outer query.  SELECT select_list FROM table WHERE expression operator (SELECT select_list FROM table);

4. Subquery example  SELECT last_name FROM employees WHERE salary > (SELECT salary FROM employees WHERE employee_id = 104); Marge Hohly4

5. 5 SUBQUERIES  Guidelines for using subqueries are: The subquery is enclosed in parentheses. The subquery is placed on the right side of the comparison condition. The outer and inner queries can get data from different tables. Only one ORDER BY clause can be used for a SELECT statement; and, if specified, it must be the last clause in the main(outer) SELECT statement. The only limit on the number of subqueries is the buffer size the query uses.

6. Marge Hohly6 SUBQUERIES  There are two types of subqueries: Single-row subqueries that use single- row operators (>,=.>=,,<=) and return only one row from the inner query. Multiple-row subqueries that use multiple-row operators (IN, ANY, ALL) and return more than one row from the inner query.

7. Single-Row Subqueries  Return only one row  Use single-row comparison operators (=, >,>=, )  Always:  Enclose the subquery in parentheses  Place the subquery on the right hand side of the comparison condition. Marge Hohly7

8. Single-row subqueries  The outer and inner queries can get data from different tables  Only one ORDER BY clause can be used for a SELECT statement, and if specified, it must be the last clause in the main SELECT statement  The only limit on the number of subqueries is the buffer size that the query uses. Marge Hohly8

9. 9 SINGLE-ROW SUBQUERY  SELECT last_name FROM employees WHERE salary > (SELECT salary FROM employees WHERE last_name = ‘Abel’); Subquery returns 11000, thus the main SELECT statement returns all employees with a salary greater than 11000. What if there is more than one Abel in the company??

10. Subquery  SELECT last_name FROM employees WHERE department_id = (SELECT department_id FROM employees WHERE last_name = ‘Grant’); Marge Hohly10

11. Subqueries from Different Tables  The outer and inner queries can get data from different tables.  Who works in the Marketing department? SELECT last_name, job_id, department_id FROM employees WHERE department_id = (SELECT department_id FROM departments WHERE department_name = ‘Marketing’) ORDER BY job_id; Marge Hohly11

12. Subqueries from Different Tables  Group functions can be used in subqueries. A group function without a GROUP BY clause in the subquery returns a single row.  Which Global Fast Foods staff earn less than the maximum salary? SELECT last_name, first_name, salary FROM f_staffs WHERE salary < (SELECT MAX(salary) FROM f_staffs); Marge Hohly12

13. Marge Hohly13 Error Example  SELECT department_id, department_name FROM departments WHERE department_id = (SELECT department_id FROM employees WHERE salary < 4000);  What will result?

14. Marge Hohly14 SUBQUERIES FROM DIFFERENT TABLES  Subqueries are not limited to just one inner query. As the example illustrates, there can be more than one subquery returning information to the outer query. Also, the outer and inner queries can get data from different tables.  SELECT last_name,job_id,salary,department_id FROM employees WHERE job_id= (SELECT job_id FROM employees WHERE employee_id = 141) AND department_id = (SELECT department_id FROM departments WHERE location_id = 1500);  Subquery returns job_id = ST_CLERK and department_id = 50

15. Marge Hohly15 Results of previous query

16. Marge Hohly16 SUBQUERIES  Group functions can be used in single-row subqueries. The inner query returns a single row to the outer query. SELECT last_name,first_name,salary FROM f_staffs WHERE salary < (SELECT MAX(salary) FROM f_staffs);

17. Marge Hohly17 Example results  Subquery returns MAX(salary) = 60

18. GROUP Functions in HAVING Clause  Subqueries can also be placed in the HAVING clause.  Remember that the HAVING clause is similar to the WHERE clause, except that the HAVING clause is used to restrict groups and always has a group condition (such as MIN, MAX, AVG) stated.  Because the HAVING clause always has a group condition, the subquery will nearly always have a group condition as well. Marge Hohly18

19. Marge Hohly19 GROUP Functions in HAVING Clause  HAVING clause is used to restrict groups and always has a group condition (such as MIN, MAX, AVG) stated  See next page for example

20. Marge Hohly20 GROUP Functions in HAVING Clause  SELECT department_id, MIN(salary) FROM employees GROUP BY department_id HAVING MIN(salary) > (SELECT MIN(salary) FROM employees WHERE department_id = 50);  Inner query returns 7500 for minimum salary

21. Marge Hohly21 Multi-row subquery

22. Multiple-Column Subqueries SELECT employee_id, manager_id, department_id FROM employees WHERE (manager_id,department_id) IN (SELECT manager_id,department_id FROM employees WHERE employee_id IN (149,176)) AND employee_id NOT IN (149,176);  Subqueries can use one or more columns. If they use more than one column, they are called multiple-column subqueries. A multiple-column subquery can be either pair-wise comparisons or non-pair-wise comparisons. Marge Hohly22

23. Multiple-Column Subqueries  Non-pair-wise multiple-column subquery uses more than one column  It compares them one at a time  Comparisons take place in different subqueries  Write one subquery per column Marge Hohly23

24. Multiple-Column Subqueries SELECT employee_id, manager_id, department_id FROM employees WHERE manager_id IN (SELECT manager_id FROM employees WHERE employee_id IN (176,149)) AND department_id IN (SELECT department_id FROM employees WHERE employee_id IN (176,149)) AND employee_id NOT IN(174,199); Marge Hohly24

25. Marge Hohly25 Example  Write a query to find the name of the Global Fast Foods employee who makes the most money?  Solution next slide

26. Marge Hohly26 Solution using subquery

27. EXIST & NOT EXIST in Subqueries  EXIST and its opposite NOT EXIST are another two clauses that can be used when testing for matches in subqueries. EXISTS test for a TRUE, or a matching result in the subquery.  If you wanted to see how many employees were only employees and not also a manager, you could use NOT EXIST: SELECT count(*) FROM employees t1 WHERE NOT EXISTS (SELECT NULL FROM employees t2 WHERE t2.manager_id = t1.employee_id );  In this example the subquery is selecting a NULL value to emphasize the fact that we are testing for an occurrence of rows in the subquery, we are not wanting to return anything but TRUE or FALSE from it. Marge Hohly27

28. EXIST & NOT EXIST in Subqueries SELECT count(*) FROM employees t1 WHERE t1.employee_id NOT IN (SELECT t2.manager_id FROM employees t2 );  Same as previous query with NOT IN rather than NOT EXIST  Different results – Why?  Beware of NULLS in subqueries – NOT EXISTS safer Marge Hohly28

29. EXIST & NOT EXIST in Subqueries FOR x IN ( SELECT * FROM employees t1 ) LOOP IF ( EXISTS ( SELECT NULL FROM employees t2 WHERE t1.emplolyee_id = t2.manager_id ) THEN OUTPUT THE RECORD END IF END LOOP  EXISTS executed a Full Table Scan of outer table then loops through the subquery results Marge Hohly29

30. EXIST & NOT EXIST in Subqueries  One final not about EXISTS and IN.  IN will generally execute faster, as it can use any existing indexes on the outer table, which EXISTS cannot, but it does depend on the size of the tables; which one of the expressions will run faster.  A small outer table joined to a very big inner table can still execute very fast using EXISTS, perhaps even faster that the same statement using IN.  And remember: be careful when handling NULLs. Marge Hohly30

31. Single-row vs. Multiple-row SELECT first_name, last_name FROM employees WHERE salary = (SELECT salary FROM employees WHERE department_id = 20); Marge Hohly31

32. Single-row vs. Multiple-row  Whose salary is equal to the salary of an employee in department 20 ?  Why does this example not work? Because there is more than one employee in department 20, so the subquery returns multiple rows. We call this a multiple-row subquery.  The problem is the equals sign (=) in the WHERE condition.  How can one value be equal to (or not equal to) more than one value? It’s a silly question, isn’t it?  Error Code: ORA-01427: single-row subquery returns more than one row Marge Hohly32

33. Marge Hohly33 Multiple-Row Subqueries  Subqueries that return more than one value are called multiple-row subqueries  When used in a WHERE clause, the multiple-row subquery must use a multiple- row operator, such as IN, ANY, or ALL.  The multiple-row operators are: IN ANY ALL  The NOT operator can be used with any of these three operators See example on next slide

34. Marge Hohly34 Multiple-Row Subqueries cont’d  SELECT employee_id, last_name, salary, department_id FROM employees WHERE salary NOT IN (SELECT salary FROM employees WHERE last_name = ‘King’);

35. Marge Hohly35 IN  SELECT last_name,salary, department_id FROM employees Where salary IN(SELECT MIN(salary) FROM employees GROUP BY department_id);

36. Marge Hohly36 ANY  The ANY operator compares a value to each value returned by a subquery.  SELECT employee_id, last_name, job_id, salary FROM employees WHERE salary < ANY (SELECT salary FROM employees WHERE job_id = ‘IT_PROG’);  Results next slide

37. Marge Hohly37 Results of ANY

38. Marge Hohly38 All  Used when the outer- query WHERE clause is designed to restrict rows based on all values returned from the inner query.  the inner query will return a list of values.  The ALL operator compares a value to every value returned by the inner query.

39. Marge Hohly39 NULL Values in Subqueries SELECT emp.last_name FROM employees emp WHERE emp.employee_id NOT IN (SELECT mgr.manager_id FROM employees mgr); SQL Query Results No Data One of the values returned by the inner query is a null value, and hence the entire query returns no rows. King does not have a manager. MANAGER_ID - 100 102 103 100 124 100 149

40. Marge Hohly40 NULL Example  SELECT department_id, department_name FROM departments WHERE department_id = (SELECT department_id FROM employees WHERE salary >60000); SQL Query Results. No data found. No employee has a salary >60000 There is no such thing as = NULL as NULL is not zero!

41. Marge Hohly41 Null Values in Subqueries, cont’d  SELECT emp.last_name FROM employees emp WHERE emp.employee_id NOT IN (SELECT mgr.manager_id FROM employees mgr WHERE mgr.manager_id IS NOT NULL);  View results of inner query on next slide.  Now, none of the values returned by the inner query is a null value, thus it works.

42. Marge Hohly42 Results of Inner Query

43. Marge Hohly43 Examples  1. Select all the employees (name, job ID, salary) in departments 10 and 30. Write two different queries that will produce the desired result.  2. Select the name of all the departments (department name and location id) and order by department number. Do not display the department number in the output.

44. Marge Hohly44 Possible Answers to examples 1. a.SELECT last_name,job_id, salary FROM employees WHERE department_id in (10,30); b.SELECT last_name,job_id, salary FROM employees WHERE department_id = 10 or department_id=30; c.This is not the most efficient answer, but it does return the correct results: SELECT last_name,job_id,salary FROM employees WHERE department_id IN( SELECT department_id FROM departments WHERE department_id IN (10,30)); 2. SELECT department_name, location_id FROM departments ORDER BY department_id;

45. Group By and Having in multi-row subqueries  If you want to find the departments whose minimum salary is less than the salary of any employee who works in departments 10 or 20?  SELECT department_id,MIN(salary) FROM employees GROUP BY department_id HAVING MIN(salary) <ANY (SELECT salary FROM employees WHERE department_id IN (10,20)); Marge Hohly45

46. GROUP BY and HAVING  You can have a GROUP BY in the subquery  Which departments have a minimum salaries in departments less than 50?  SELECT department_id, MIN(salary) FROM employees GROUP BY department_id HAVING MIN(salary)>ALL (SELECT MIN(salary) FROM employees WHERE department_id <50 GROUP BY department_id); Marge Hohly46

47. Single-row vs. multi-row subqueries  If you believe there is a possibility that the inner query could return more than one value write a multi- row subquery.  When in doubt use a multi-row subquery. It is better to be safe than sorry. Marge Hohly47

48. Single-row vs. multi-row subqueries  ONE LAST POINT ABOUT SUBQUERIES  It would be better to write a multiple- row subquery.  The multiple-row subquery syntax will still work even if the subquery returns a single row.  If in doubt, write a multiple-row subquery ! Marge Hohly48

49. Correlated Subqueries Marge Hohly49

50. Correlated Subqueries  Whose salary is higher than the average salary of their department?  To answer that question we need to write a correlated subquery. Correlated subqueries are used for row-by-row processing.  Each subquery is executed once for every row of the outer query.  With a normal subquery, the inner SELECT query runs first and executes once, returning values to be used by the main query. A correlated subquery, however, executes once for each candidate row considered by the outer query. In other words, the inner query is driven by the outer query. The part that makes this example a correlated subquery is marked in red. Marge Hohly50

51. Correlated Subquery SELECT o.first_name, o.last_name, o.salary FROM employees o WHERE o.salary > (SELECT AVG(i.salary) FROM employees i WHERE i.department_id = o.department_id); Marge Hohly51

52. WITH clause  If you have to write a very complex query with joins and aggregations used many times, you can write the different parts of the statement as query blocks and then use those same query block in a SELECT statement. Oracle allows you to write named subqueries in one single statement, as long as you start your statement with the keyword WITH.  The WITH clause retrieves the results of one or more query blocks and stores those results for the user who runs the query.  The WITH clause improves performance.  The WITH clause makes the query easier to read. Marge Hohly52

53. WITH clause  The syntax for the WITH clause is as follows:  WITH subquery-name AS (subquery), subquery-name AS (subquery) SELECT column-list FROM {table | subquery-name | view} WHERE condition is true; Marge Hohly53

54. WITH clause  Write the query for the following requirement:  Display the department name and total salaries for those departments whose total salary is greater than the average salary across departments.  To solve this query you will need to first get the total salaries per department, then the average salary per department and then you can list just the ones with total salary greater than the average of all departments. Marge Hohly54

55. WITH clause  Let’s examine an example of a WITH clause.  Let’s start by creating two subqueries, one called dept_costs and a second called avg_cost. Avg_cost uses the result of dept_cost and once these two subqueries have been run the actual query itself is executed.  The query itself selects from both dept_cost and avg_cost. By creating the subqueries first, you do not need to create two temporary tables to hold the results of the SUM of salary per department and the AVG of department salaries. Marge Hohly55

56. WITH clause WITH dept_costs AS ( SELECT d.department_name, SUM(e.salary) AS dept_total FROM employees e JOIN departments d ON e.department_id = d.department_id GROUP BY d.department_name), avg_cost AS ( SELECT SUM(dept_total)/COUNT(*) AS dept_avg FROM dept_costs) SELECT * FROM dept_costs WHERE dept_total > (SELECT dept_avg FROM avg_cost) ORDER BY department_name; Marge Hohly56