Displaying Data From Multiple Tables
Displaying Data From Multiple Tables
Objectives
After completing this lesson, you should be able to do the following: Write SELECT statements to access data from more than one table using eguality and nonequality joins View data that generally does not meet a join condition by using outer joins Join a table to itself
Lesson Aim This lesson covers how to obtain data from more than one table, using the different methods available.
SELECT e.empno, e.deptno, d.loc FROM emp e, dept d WHERE e.deptno = d.deptno;
Data from Multiple Tables Sometimes you need to use data from more than one table. In the slide example, the report displays data from two separate tables. EMPNO exists in the EMP table DEPTNO exists in both the EMP and DEPT the Tables. LOC exists in the DEPT table. To prodce the report. you need to link EMP and DEPT tables and access data from both of them.
Cartesian Product
A Cartesian product is formed when: A join condition is omitted A join condition is invalid All rows in the first table are joined to all rows in the second table
To avoid a Cartesian product, always include a valid join condition in a WHERE clause.
56 Rows Selected
What Is a Join?
Use a join to query data from more than one table.
Write the join condition in the WHERE clause. Prefix the column name with the table name when the same column name appears in more than one table.
Defining Joins When data from more than one table in the database is required, a join condition is used. Rows in one table can be joined to rows in another table according to common values existing in corresponding columns, that is, usually primary and foreign key columns. TO display data from two or more related tables, write a simple join condition in the WHERE clause, in the syntax: Table1.column1 denotes the table and column from which data is retrieved
Table1. column1 = is the condition that joins (or relates) the tables together table2. column2
Types of Joins
Equijoin Non-equijoin Outer join
Self join
Types of Joins
There are wo main types of join conditions: Equijoins Non-equijoins Additional join methods include the following Outerjoins Selfjoins Set Operators Note: Set operators are not covered in this course .They are covered in another SQL course.
What Is an Equijoin?
Equijoins To determine the name of an employees department, you compare the value in the DEPTNO column in the EMP table with the DEPTNO values in the DEPT table. The relationship between the EMP and DEPT table is an equijoin - that is, values in the DEPTNO column on both tables must be equal. Frequently, this type of join involves primary and foreign key complements. Note: Equijoins are also called simple joins or innerjoins.
Retrieving Records with Equijoins in the slide examaple. The SELECT clause specifies the column names to retrieve: - employee name, employee number, and department number, which are columns in the emp table - department number, department name, and location, which are columns in the DEPT table. The FROM clause specifies the two tables that the database must access: EMP table DEPT table The WHERE clause specifies how the tables are to be joined: EMP.DEPTNO=DEPT.DEPTNO
10
Qualifying Ambiguous Column Names You need to gualify the names of the columns in the WHERE clause ""itli the table names to avoid ambiguity without the table prefixes. the DEPTNO column could be from either the DEPT table or the EMP table. It is necessary to add the table prefix to execute your query.
If there are no common column names between the two tables, there is no need to qualify the columns. Howevwr, you will gain improved performance by using the table prefix because you tell the Oracle Server exactly where to find the columns.
11
SELECT e.empno, e.ename, e.deptno, d.deptno, d.loc FROM emp e, dept d WHERE e.deptno = d.deptno;
EMPNO ENAME DEPTNO 30 20 30 DEPTNO LOC 30 CHICAGO 20 DALLAS 30 CHICAGO
12
EQUIJOIN
SELECT EMP.EMPNO, EMP.ENAME, EMP.DEPTNO, DEPT.DEPTNO, DEPT.LOC FROM EMP, DEPT WHERE EMP.DEPTNO = DEPT.DEPTNO ;
EMPNO
ENAME
DEPTNO 30 20
DEPTNO
14 rows selected. SELECT e.ename, e.deptno, d.dname FROM emp e , dept d WHERE e.deptno = d.deptno ; ENAME BLAKE SMITH 14 rows selected. DEPTNO 30 SALES 20 RESEARCH DNAME
13
SELECT EMP.EMPNO, EMP.ENAME, EMP.DEPTNO, DEPT.DEPTNO, DEPT.LOC FROM EMP, DEPT WHERE EMP.DEPTNO = DEPT.DEPTNO AND INITCAP(ename) = 'King' ; EMPNO ENAME DEPTNO 10 DEPTNO LOC 10 NEW YORK
7839 KING
SELECT e.ename, e.sal, s.grade FROM EMP e, SALGRADE s WHERE e.sal BETWEEN s.losal AND s.hisal ; ENAME SMITH JAMES 14 rows selected. SAL 800 950 GRADE 1 1
14
SELECT e.ename, e.deptno, d.dname, s.grade FROM EMP e, DEPT d, salgrade s WHERE e.deptno = d.deptno AND e.sal BETWEEN s.losal AND hisal;
ENAME KING CLARK MILLER FORD SCOTT JONES ADAMS SMITH BLAKE ALLEN TURNER MARTIN WARD JAMES 14 rows selected.
DEPTNO
DNAME 10 ACCOUNTING 10 ACCOUNTING 10 ACCOUNTING 20 RESEARCH 20 RESEARCH 20 RESEARCH 20 RESEARCH 20 RESEARCH 30 SALES 30 SALES 30 SALES 30 SALES 30 SALES 30 SALES
GRADE 5 4 2 4 4 4 1 1 4 3 3 2 2 1
15
Non-Equijoins
The relationship between the EMP table and the SALGRADE table is a non-equijoin, meaning that no column in the EMP table corresponds directly to a column in the SALGRADE table. The relationship between the two tables is that the SAL column in the EMP table is between the LOSAL and HISAL column of the SALGRADE table. The relationship is obtained using an operator other than equal (=). EMPNO ENAME JOB MGR HIREDATE SAL COMM DEPTNO 7839 01/05/1981 2850 30
14 rows selected.
GRADE 1
LOSAL 700
HISAL 1200
5 rows selected.
Salary in the EMP table is between low salary and high salary in the SALGRADE table.
SELECT e . ename , e . sal , s . grade FROM emp e, salgrade s WHERE e.sal BETWEEN s.losal AND s.hisal;
GRADE 1 1
14 rows selected.
16
ENAME TURNER WARD ALLEN MARTIN TURNER WARD ALLEN MARTIN MARTIN 9 rows selected.
SAL 1500 1250 1600 1250 1500 1250 1600 1250 1250
GRADE 1 1 1 1 2 2 2 2 3
Non-Equijoins (continued) The slide example creates a non-equijoin to evaluate an employee's salary grade. The salary must be between any pair of the low and high salary ranges. It is important to note that all employees appear exactly once when this query is executed. No employee is repeated in the list. There are two reasons for this: None of the rows in the salary grade table contain grades that overlap. That is, the salary value for an employee can only lie between the low salary and high salary values of one of the rows in the salary grade table. All of the employees' salaries lie within the limits provided by the salary grade table. That is, no employee earns less than the lowest value contained in the LOSAL column or more than the highest value contained in the HISAL column. Note: Other operators such as <= and >= could be used, but BETWEEN is the simplest. Remember to specify the low value first and the high value last when using BETWEEN. Table aliases have been specified for performance reasons, not because of possible ambiguity.
17
Outer Joins
No employee in the OPERATIONS department
SELECT e.ename, e.deptno, d.dname FROM emp e, dept d WHERE e.deptno = d.deptno;
ENAME SMITH ALLEN WARD JONES MARTIN BLAKE CLARK SCOTT KING TURNER ADAMS JAMES FORD MILLER 14 rows selected. DEPTNO 20 RESEARCH 30 SALES 30 SALES 20 RESEARCH 30 SALES 30 SALES 10 ACCOUNTING 20 RESEARCH 10 ACCOUNTING 30 SALES 20 RESEARCH 30 SALES 20 RESEARCH 10 ACCOUNTING DNAME
18
Outer Joins
Returning Records with No Direct Match with Outer Joins If a row does not satisfy a join condition, the row will not appear in the query result. For example, in the equijoin condition of EMP and DEPT tables, department OPERATIONS does not appear because no one works in that department.
19
Outer Joins
You use an outer join to also see rows that do not usually meet the join condition. Outer join operator is the plus sign (+). SELECT tablel.column, table2. column FROM tablel, table2 WHERE tablel.column(+) = table2.column; SELECT tablel.column, table2.column FROM tablel, table2 WHERE tablel.column. = table2. column {+) ;
Returning Records with No Direct Match with Outer Joins The missing row(s) can be returned if an outerjoin operator is used in the join condition. The operator is a plus sign enclosed in parenthesis (+), and it is placed on the "side" of the equality that the join rhctt a defcient in mfrmcnun. This operator has the effect of creating one or more mil l rows, to which one or more rows from the nondeficient table can be joined in the syntax. In the condition that joins (or relates) the lables together, is the outer join symbol, which can be placed on either side of the WHERE clause condition, but not on both sides (Place the outer join symbol following the name of the column in the table without the matching rows.)
20
OUTER JOIN
Previously, we had looked at left join, or inner join, where we select rows common to the participating tables to a join. What about the cases where we are interested in selecting elements in a table regardless of whether they are present in the second table? We will now need to use the SQL OUTER JOIN command. The syntax for performing an outer join in SQL is database-dependent. For example, in Oracle, we will place an "(+)" in the WHERE clause on the other side of the table for which we want to include all the rows. Let's assume that we have the following two tables, Table Store_Information store_name Los Angeles San Diego Los Angeles Boston Table Geography region_name East East West West store_name Boston New York Los Angeles San Diego Sales $1500 $250 $300 $700 Date Jan-05-1999 Jan-07-1999 Jan-08-1999 Jan-08-1999
and we want to find out the sales amount for all of the stores. If we do a regular join, we will not be able to get what we want because we will have missed "New York," since it does not appear in the Store_Information table. Therefore, we need to perform an outer join on the two tables above:
21
OUTER JOIN SELECT A1.store_name, SUM(A2.Sales) SALES FROM Geography A1, Store_Information A2 WHERE A1.store_name = A2.store_name (+) GROUP BY A1.store_name Note that in this case, we are using the Oracle syntax for outer join. Result:
store_name Boston New York Los Angeles San Diego $1800 $250 SALES $700
Note: NULL is returned when there is no match on the second table. In this case, "New York" does not appear in the table Store_Information, thus its corresponding "SALES" column is NULL. SELECT e.ename, d.DEPTNO, d.dname FROM emp e, dept d WHERE e.deptno(+) = d.deptno ORDER BY e.deptno; ENAME ALLEN WARD DEPTNO 30 SALES 30 SALES 40 OPERATIONS 15 rows selected. DNAME
22
Outer Joins
Returning Records with No Direct Match with Outer Joins
If a row does not satisfy a join condition, the row will not appear in the query result. For example, in the equijoin condition of EMP and DEPT tables, department OPERATIONS does not appear because no one works in that department. SELECT e.ename , e.deptno, d.dname FROM emp e, dept d WHERE e.deptno = d.deptno;
ENAME BLAKE SMITH ALLEN WARD JONES MARTIN CLARK SCOTT KING TURNER ADAMS JAMES FORD MILLER 14 rows selected. DEPTNO 30 SALES 20 RESEARCH 30 SALES 30 SALES 20 RESEARCH 30 SALES 10 ACCOUNTING 20 RESEARCH 10 ACCOUNTING 30 SALES 20 RESEARCH 30 SALES 20 RESEARCH 10 ACCOUNTING DNAME
23
Using Outer Joins SELECT e.ename, d.DEPTNO, d.dname FROM emp e, dept d WHERE e.deptno(+) = d.deptno ORDER BY e.deptno;
ENAME MILLER KING CLARK SMITH FORD ADAMS SCOTT JONES TURNER JAMES ALLEN MARTIN BLAKE WARD
DEPTNO 10 ACCOUNTING 10 ACCOUNTING 10 ACCOUNTING 20 RESEARCH 20 RESEARCH 20 RESEARCH 20 RESEARCH 20 RESEARCH 30 SALES 30 SALES 30 SALES 30 SALES 30 SALES 30 SALES 40 OPERATIONS
DNAME
15 rows selected.
24
SQL JOIN
Now we want to look at joins. To do joins correctly in SQL requires many of the elements we have introduced so far. Let's assume that we have the following two tables, Table Store_Information store_name Los Angeles San Diego Los Angeles Boston Table Geography region_name East East West West store_name Boston New York Los Angeles San Diego Sales $1500 $250 $300 $700 Date Jan-05-1999 Jan-07-1999 Jan-08-1999 Jan-08-1999
and we want to find out sales by region. We see that table Geography includes information on regions and stores, and table Store_Information contains sales information for each store. To get the sales information by region, we have to combine the information from the two tables. Examining the two tables, we find that they are linked via the common field, "store_name". We will first present the SQL statement and explain the use of each segment later:
25
The first two lines tell SQL to select two fields, the first one is the field "region_name" from table Geography (aliased as REGION), and the second one is the sum of the field "Sales" from table Store_Information (aliased as SALES). Notice how the table aliases are used here: Geography is aliased as A1, and Store_Information is aliased as A2. Without the aliasing, the first line would become SELECT Geography.region_name REGION, SUM(Store_Information.Sales) SALES which is much more cumbersome. In essence, table aliases make the entire SQL statement easier to understand, especially when multiple tables are included. Next, we turn our attention to line 3, the WHERE statement. This is where the condition of the join is specified. In this case, we want to make sure that the content in "store_name" in table Geography matches that in table Store_Information, and the way to do it is to set them equal. This WHERE statement is essential in making sure you get the correct output. Without the correct WHERE statement, a Cartesian Join will result. Cartesian joins will result in the query returning every possible combination of the two (or whatever the number of tables in the FROM statement) tables. In this case, a Cartesian join would result in a total of 4 x 4 = 16 rows being returned.
26
Self Joins
MGR in the WORKER table is equal to EMPNO in the MANAGER table.
SELECT e.ename, e.empno , m.ename, m.empno FROM emp e, emp m WHERE e.mgr = m.empno ;
ENAME JAMES TURNER MARTIN WARD ALLEN FORD SCOTT MILLER ADAMS CLARK JONES BLAKE SMITH 13 rows selected. EMPNO ENAME 7900 BLAKE 7844 BLAKE 7654 BLAKE 7521 BLAKE 7499 BLAKE 7902 JONES 7788 JONES 7934 CLARK 7876 SCOTT 7782 KING 7566 KING 7698 KING 7369 FORD EMPNO 7698 7698 7698 7698 7698 7566 7566 7782 7788 7839 7839 7839 7902
27
SELF JOINS SELECT worker.ename || 'works for ' || manager.ename FROM emp worker, emp manager WHERE worker.mgr = manager.empno; WORKER.ENAME||'WORKSFOR'||MANAGER.ENAME JAMESworks for BLAKE TURNERworks for BLAKE 13 rows selected.
Joining a Table to Itself (continued) The slide example joins the EMP table to itself. To simulate two tables in the FROM clause, there are two aliases, namely WORKER and MANAGER, for the same table EMP. In this example, the WHERE clause contains the join that means ''where a worker's manager number matches the employee number for the manager.
28
Self Joins
SELECT e.ename, e.empno , m.ename, m.empno FROM emp e, emp m WHERE e.mgr = m.empno; ENAME JAMES TURNER EMPNO ENAME 7900 BLAKE 7844 BLAKE EMPNO 7698 7698
13 rows selected.
Joining a Table to Itself Sometimes you need to join a table to itself. To find the name of each employee's manager, you need to join the EMP table to itself, or perform a self join. For example, to find the name of Blake's manager, you need to: Find Blake in the EMP table by looking at the ENAME column. Find the manager number for Blake by looking at the MGR column. Blake's manager number is 7839. Find the name of the manager with EMPNO 7839 by looking at the ENAME column. King's employee number is 7839, so King is Blake's manager. In this process, you look in the table twice. The first time you look in the table to find Blake in the ENAME column and MGR value of 7839. The second time you look in the EMPNO column to find 7839 and the ENAME column to find King
29
Summary
SELECT tablel. Column , table2. column FROM tablel , table2 WHERE tablel. columnl = table2. column2;
Equijoin Non-equijoin Outer join Self join
Summary There are multiple ways to join tables. The common thread, though, is that you want to link them through a condition in the WHERE clause. The method you choose will be based on the required result and the data structures that you are using.
30
Exercices
Solution 1 SELECT e.ename, e.deptno, d.dname FROM emp e , dept d WHERE e.deptno = d.deptno ; Solution 2 SELECT e.job, d.loc FROM emp e , dept d WHERE e.deptno = d.deptno AND e.deptno = 30; Solution 3 SELECT e.ename, d.dname, d.loc FROM emp e , dept d WHERE comm IS NOT NULL AND e.deptno = d.deptno ; Solution 4 SELECT e.ename, d.dname, d.loc FROM emp e , dept d WHERE comm IS NOT NULL AND e.deptno = d.deptno ; Solution 5 SELECT e.ename, e.job, e.deptno, d.dname FROM emp e, dept d WHERE e.deptno = d.deptno AND d.loc = 'DALLAS' ;
Solution 6 SELECT e.ename "i" , e.empno "i No" , m.ename "Manager" , m.empno "Mgr No" FROM emp e, emp m WHERE e.mgr = m.empno ;
Solution 7 SELECT e.ename "i" , e.empno "i No" , m.ename "Manager" , m.empno "Mgr No" FROM emp e, emp m WHERE e.mgr = m.empno(+) ;
31
Solution 8a SELECT e.deptno "Blm" , e.ename "i" , b.ename FROM emp e , emp b WHERE e.deptno = b.deptno ORDER BY e.empno ;
Solution 8b SELECT e.deptno "Blm" , e.ename "i" , b.ename FROM emp e , emp b WHERE e.deptno = b.deptno AND e.ename != b.ename ORDER BY e.empno ; Solution 8c SELECT e.deptno "Blm" , e.ename "i" , b.ename FROM emp e , emp b WHERE e.deptno = b.deptno AND e.ename <> b.ename ORDER BY e.deptno ; Solution 9a DESC salgrade; Solution 9b SELECT e.ename "i" , e.job "i" , d.dname "Blm" , e.sal "Maa" , s.grade "Barem" FROM emp e, dept d , salgrade s WHERE e.deptno = d.deptno AND e.sal BETWEEN s.losal AND s.hisal ;
Solution 10 SELECT e.ename "i" , e.hiredate "e Giri Tarihi" , b.hiredate "Blake" FROM emp e, emp b WHERE e.hiredate > b.hiredate AND b.ename = 'BLAKE' ;
Solution 11 SELECT e.ename "i" , e.hiredate "e Giri Tarihi" , m.ename "Manageri" , m.hiredate "Managerin Giri Tar" FROM emp e, emp m WHERE e.hiredate < m.hiredate AND e.mgr = m.empno ;
32