Jointures

Displaying Data from
Multiple Tables
www.supinfo.com
Copyright © SUPINFO. All rights reserved
Displaying Data from Multiple Tables
Course objectives
By completing this course, you will be able to:
 Write SELECT statements to

access data from more than
one table using equijoins and
nonequijoins
 Join a table to itself by using a
self-join
 View data that generally does
not meet a join condition by
using outer joins
 Generate a Cartesian product
of all rows from two or more
tables
Course topics
Course’s plan:
 Displaying Data from
Multiple Tables
Displaying Data from

Multiple Tables
Preview
 Joins: Presentation.
 Types of joins.
 Qualifying Ambiguous Column
Names.
 Natural Joins.
 The ON Clause.
 Non-equijoins.
 Outer Joins.
 Cross Joins.
Joins: Presentation
EMPLOYEES DEPARTMENTS
Types of Joins
Joins that are compliant with the SQL:1999 standard
include the following:
 Cross joins
 Natural joins
 USING clause
 Full (or two-sided) outer joins
 Arbitrary join conditions for outer joins
Types of Joins
Joining Tables Using SQL:1999 Syntax:
SELECT table1.column, table2.column

FROM table1
[NATURAL JOIN table2] |
[JOIN table2
USING (column_name)] |
[JOIN table2
ON (table1.column_name = table2.column_name)]|
[LEFT|RIGHT|FULL OUTER JOIN table2
ON (table1.column_name = table2.column_name)]|
[CROSS JOIN table2];
Qualifying Ambiguous Column Names

 Use table prefixes to qualify column names that are in
multiple tables.
 Use table prefixes to improve performance.
 Use column aliases to distinguish columns that have
identical names but reside in different tables.
 Do not use aliases on columns that are identified in the
USING clause and listed elsewhere in the SQL statement.
Qualifying Ambiguous Column Names

Using Table Aliases:
 Use table aliases to simplify queries.
 Use table aliases to improve performance.
SELECT e.employee_id, e.last_name,

d.location_id, department_id
FROM employees e JOIN departments d
USING (department_id) ;
Natural Joins
Creating Natural Joins:
 The NATURAL JOIN clause is based on all columns in the
two tables that have the same name.
 It selects rows from the two tables that have equal values
in all matched columns.
 If the columns having the same names have different data
types, an error is returned.
Natural Joins
Retrieving Records with Natural Joins:
SELECT department_id, department_name,

location_id, city
FROM departments
NATURAL JOIN locations ;
Natural Joins
Creating Joins with the USING Clause:
 If several columns have the same names but the data
types do not match, the NATURAL JOIN clause can be
modified with the USING clause to specify the columns
that should be used for an equijoin.
 Use the USING clause to match only one column when
more than one column matches.
 Do not use a table name or alias in the referenced
columns.
 The NATURAL JOIN and USING clauses are mutually
exclusive.
Natural Joins
Joining Column Names:
… …
Foreign key Primary key

Natural Joins
Retrieving Records with the USING Clause:
SELECT employees.employee_id, employees.last_name,

departments.location_id, department_id
FROM employees JOIN departments
USING (department_id) ;
The ON Clause
Creating Joins with the ON Clause:
 The join condition for the natural join is basically an
equijoin of all columns with the same name.
 Use the ON clause to specify arbitrary conditions or
specify columns to join.
 The join condition is separated from other search
conditions.
 The ON clause makes code easy to understand.
The ON Clause
Retrieving Records with the ON Clause:
SELECT e.employee_id, e.last_name, e.department_id,

d.department_id, d.location_id
ON (e.department_id = d.department_id) ;
The ON Clause
Self-Joins Using the ON Clause:
EMPLOYEES (WORKER) EMPLOYEES (MANAGER)
MANAGER_ID in the WORKER table is

equal to EMPLOYEE_ID in the
MANAGER table.
The ON Clause
Self-Joins Using the ON Clause:
SELECT e.last_name emp, m.last_name mgr

FROM employees e JOIN employees m
ON (e.manager_id = m.employee_id);
The ON Clause
Applying Additional Conditions to a Join:
SELECT e.employee_id, e.last_name, e.department_id,

d.department_id, d.location_id
ON (e.department_id = d.department_id)
AND e.manager_id = 149 ;
The ON Clause
Creating Three-Way Joins with the ON Clause:
SELECT employee_id, city, department_name

FROM employees e
JOIN departments d
ON d.department_id = e.department_id
JOIN locations l
ON d.location_id = l.location_id;
Non-equijoins
EMPLOYEES JOB_GRADES
Salary in the EMPLOYEES

table must be between
lowest salary and highest
salary in the JOB_GRADES
table.
Non-equijoins
Retrieving Records with Non-Equijoins:
SELECT e.last_name, e.salary, j.grade_level

FROM employees e JOIN job_grades j
ON e.salary BETWEEN
j.lowest_sal AND j.highest_sal ;
Outer Joins
DEPARTMENTS EMPLOYEES
There are no employees in

department 190.
Outer Joins
INNER Versus OUTER Joins:
 In SQL:1999, the join of two tables returning only
matched rows is called an inner join.
 A join between two tables that returns the results of the
inner join as well as the unmatched rows from the left (or
right) tables is called a left (or right) outer join.
 A join between two tables that returns the results of an
inner join as well as the results of a left and right join is a
full outer join.
Outer Joins
LEFT OUTER JOIN:
SELECT e.last_name, e.department_id, d.department_name

FROM employees e LEFT OUTER JOIN departments d
Outer Joins
RIGHT OUTER JOIN:
SELECT e.last_name, e.department_id, d.department_name

FROM employees e RIGHT OUTER JOIN departments d
Outer Joins
FULL OUTER JOIN:
SELECT e.last_name, d.department_id, d.department_name

FROM employees e FULL OUTER JOIN departments d
Cross Joins
Cartesian Products:
 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.
Cross Joins
Generating a Cartesian Product:
EMPLOYEES (20 rows) DEPARTMENTS (8 rows)
Cartesian product:
20 x 8 = 160 rows
Cross Joins
Creating Cross Joins:
 The CROSS JOIN clause produces the cross product of
two tables.
 This is also called a Cartesian product between the two
tables.
SELECT last_name, department_name
FROM employees
CROSS JOIN departments ;
Part 1 Stop-and-think
Do you have any questions ?

Part 1 Summary
Types of Qualifying
Joins:
joins Ambiguous
Presentation
Column
Names
Natural
Joins The ON
Clause
Non-
equijoins
Outer Cross
Joins Joins
For more
If you want to go into these subjects more deeply, …
Publications Courses
Cursus: Merise & SQL

Cursus: PL/SQL
Cursus: DBA1 & DBA2
Cursus: DWH & BIS
http://www.oracle.../bookstore/
Web sites Certifications
http://www.labo-oracle.com 1Z0-007
http://www.oracle.com
http://otn.oracle.com
Congratulations
You have successfully completed the
SUPINFO course n°4
Oracle Technologies
The end

Jointures

Uploaded by

Copyright:

Available Formats

Jointures

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Jointures

Uploaded by

Copyright:

Available Formats

Displaying Data from

 Write SELECT statements to

Displaying Data from

SELECT table1.column, table2.column

Qualifying Ambiguous Column Names

Qualifying Ambiguous Column Names

SELECT e.employee_id, e.last_name,

SELECT department_id, department_name,

Foreign key Primary key

SELECT employees.employee_id, employees.last_name,

SELECT e.employee_id, e.last_name, e.department_id,

EMPLOYEES (WORKER) EMPLOYEES (MANAGER)

MANAGER_ID in the WORKER table is

SELECT e.last_name emp, m.last_name mgr

SELECT e.employee_id, e.last_name, e.department_id,

SELECT employee_id, city, department_name

Salary in the EMPLOYEES

SELECT e.last_name, e.salary, j.grade_level

There are no employees in

SELECT e.last_name, e.department_id, d.department_name

SELECT e.last_name, e.department_id, d.department_name

SELECT e.last_name, d.department_id, d.department_name

EMPLOYEES (20 rows) DEPARTMENTS (8 rows)

Do you have any questions ?

Cursus: Merise & SQL

Web sites Certifications

You might also like