31
Database System Concepts, 6 th Ed. ©Silberschatz, Korth and Sudarshan See www.db-book.com for conditions on re-use Chapter 2: Chapter 2: Introduction to Relational Introduction to Relational Model Model

CSE 301: Database Systems Ch2

Embed Size (px)

Citation preview

Page 1: CSE 301: Database Systems Ch2

Database System Concepts, 6th Ed.

©Silberschatz, Korth and SudarshanSee www.db-book.com for conditions on re-use

Chapter 2: Chapter 2: Introduction to Relational ModelIntroduction to Relational Model

Page 2: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.2Database System Concepts - 6th Edition

Relational ModelRelational Model

The relational data model is based on a collection of tables each of which is assigned a unique name.

The user of the database system may query these tables, insert new tuples, delete tuples, and update (modify) tuples. There are several languages for expressing these operations.

Page 3: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.3Database System Concepts - 6th Edition

Example of a RelationExample of a Relation

attributes(or columns)

tuples(or rows)

Relation:

A Table

Tuple:

A Row

Attributes:

A Column header

Page 4: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.4Database System Concepts - 6th Edition

Attribute TypesAttribute Types

The set of allowed values for each attribute is called the domain of the attribute

Attribute values are (normally) required to be atomic; that is, indivisible

The special value null is a member of every domain

The null value causes complications in the definition of many operations

Page 5: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.5Database System Concepts - 6th Edition

Relation Schema and InstanceRelation Schema and Instance

The schema of a relation refers to its logical design. The schema of a relation includes its attributes, and optionally the types of the attributes and constraints on the relation such as primary and foreign key constraints.

Example: instructor(id, name, dept_name, salary)

An instance of the relation refers to its contents at a point in time.

The current values (relation instance) of a relation are specified by the rowa of a table.

An element t of r is a tuple, represented by a row in a table.

Page 6: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.6Database System Concepts - 6th Edition

Relations are UnorderedRelations are Unordered

Order of tuples is irrelevant (tuples may be stored in an arbitrary order)

Example: instructor relation with unordered tuples

Page 7: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.7Database System Concepts - 6th Edition

DatabaseDatabase

A database consists of multiple relations

Information about an enterprise is broken up into parts

instructor student advisor

Bad design: univ (instructor -ID, name, dept_name, salary, student_Id, ..)results in

repetition of information (e.g., two students have the same instructor)

the need for null values (e.g., represent an student with no advisor)

Normalization theory (Chapter 7) deals with how to design “good” relational schemas

Page 8: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.8Database System Concepts - 6th Edition

KeysKeys

Let K R

K is a superkey of R if values for K are sufficient to identify a unique tuple of each possible relation r(R)

Example: {ID} and {ID,name} are both superkeys of instructor.

Superkey K is a candidate key if K is minimal

Example: {ID} is a candidate key for Instructor

One of the candidate keys is selected to be the primary key.

which one?

Foreign key constraint: Value in one relation must appear in another

Referencing relation

Referenced relation

Page 9: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.9Database System Concepts - 6th Edition

Schema Diagram for University DatabaseSchema Diagram for University Database

Page 10: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.10Database System Concepts - 6th Edition

Relational Query LanguagesRelational Query Languages

Procedural vs.non-procedural, or declarative

Procedural: the user instructs the system to perform a sequence of operations on the database to compute the desired result.

Non-procedural: the user describes the desired information without

giving a specific procedure for obtaining that information.

“Pure” and formal languages:

Relational algebra

Tuple relational calculus

Domain relational calculus

Relational operators

Page 11: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.11Database System Concepts - 6th Edition

Selection of tuplesSelection of tuples

Relation r

Select tuples with A=B and D > 5

σ A=B and D > 5 (r)

Page 12: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.12Database System Concepts - 6th Edition

Selection of Columns (Attributes)Selection of Columns (Attributes)

Relation r:

Select A and C

Projection

Π A, C (r)

Page 13: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.13Database System Concepts - 6th Edition

Joining two relations – Cartesian ProductJoining two relations – Cartesian Product

Relations r, s:

r x s:

Page 14: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.14Database System Concepts - 6th Edition

Union of two relationsUnion of two relations

Relations r, s:

r s:

Page 15: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.15Database System Concepts - 6th Edition

Set difference of two relationsSet difference of two relations

Relations r, s:

r – s:

Page 16: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.16Database System Concepts - 6th Edition

Set Intersection of two relationsSet Intersection of two relations

Relation r, s:

r s

Page 17: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.17Database System Concepts - 6th Edition

Joining two relations – Natural JoinJoining two relations – Natural Join

Let r and s be relations on schemas R and S respectively. Then, the “natural join” of relations R and S is a relation on schema R S obtained as follows:

Consider each pair of tuples tr from r and ts from s.

If tr and ts have the same value on each of the attributes in

R S, add a tuple t to the result, where

t has the same value as tr on r

t has the same value as ts on s

Page 18: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.18Database System Concepts - 6th Edition

Natural Join ExampleNatural Join Example

Relations r, s:

Natural Join

r s

Page 19: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.19Database System Concepts - 6th Edition

Figure in-2.1Figure in-2.1

Page 20: CSE 301: Database Systems Ch2

Database System Concepts, 6th Ed.

©Silberschatz, Korth and SudarshanSee www.db-book.com for conditions on re-use

End of Chapter 2End of Chapter 2

Page 21: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.21Database System Concepts - 6th Edition

Figure 2.01Figure 2.01

Page 22: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.22Database System Concepts - 6th Edition

Figure 2.02Figure 2.02

Page 23: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.23Database System Concepts - 6th Edition

Figure 2.03Figure 2.03

Page 24: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.24Database System Concepts - 6th Edition

Figure 2.04Figure 2.04

Page 25: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.25Database System Concepts - 6th Edition

Figure 2.05Figure 2.05

Page 26: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.26Database System Concepts - 6th Edition

Figure 2.06Figure 2.06

Page 27: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.27Database System Concepts - 6th Edition

Figure 2.07Figure 2.07

Page 28: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.28Database System Concepts - 6th Edition

Figure 2.10Figure 2.10

Page 29: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.29Database System Concepts - 6th Edition

Figure 2.11Figure 2.11

Page 30: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.30Database System Concepts - 6th Edition

Figure 2.12Figure 2.12

Page 31: CSE 301: Database Systems Ch2

©Silberschatz, Korth and Sudarshan2.31Database System Concepts - 6th Edition

Figure 2.13Figure 2.13