Outline: Relational Data Model

Slides:



Advertisements
Similar presentations
Database System - Assignment #3 Sept. 2012Yangjun Chen ACS Assignment #3 due Wed., Nov. 14, (30) Exercise 7.17 on Page 235 Show the result.
Advertisements

Defined by Edgar Codd in 1970 Defined by Edgar Codd in 1970 Considered ingenious but impractical Considered ingenious but impractical Conceptually simple.
Relational Database. Relational database: a set of relations Relation: made up of 2 parts: − Schema : specifies the name of relations, plus name and type.
OUTLINE OF THE LECTURE PART I GOAL: Understand the Data Definition Statements in Fig 4.1 Step1: Columns of the Tables and Data types. Step2: Single column.
The Relational Algebra
Database technology Lecture 2: Relational databases and SQL
Data Definition Languages Atif Farid Mohammad UNCC.
Exploring Microsoft Access 2003 Chapter 4 Proficiency: Relational Databases, External Data, Charts, Pivot, and the Switchboard.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 3 The Basic (Flat) Relational Model.
Database Systems Chapter 6 ITM Relational Algebra The basic set of operations for the relational model is the relational algebra. –enable the specification.
- relation schema, relations - database schema, database state
Review Database Application Development Access Database Development ER-diagram Forms Reports Queries.
Database: Review Sept. 2009Yangjun Chen ACS Database Introduction system architecture, Basic concepts, ER-model, Data modeling, B+-tree Hashing Relational.
Relational Data Model Sept. 2014Yangjun Chen ACS Outline: Relational Data Model Relational Data Model -relation schema, relations -database schema,
Chapter 5 Relational Model Concepts Dr. Bernard Chen Ph.D. University of Central Arkansas.
CS 380 Introduction to Database Systems (Chapter 5: The Relational Data Model and Relational Database Constraints)
1 Lecture 04 The relational data Model, Relational Constraints 1.
1 The Relational Data Model, Relational Constraints, and The Relational Algebra.
Review: Application of Database Systems
Topic 5 The Relational Data Model and Relational Database Constraints Faculty of Information Science and Technology Mahanakorn University of Technology.
Instructor: Churee Techawut Basic Concepts of Relational Database Chapter 5 CS (204)321 Database System I.
DatabaseIM ISU1 Fundamentals of Database Systems Chapter 5 The Relational Data Model.
10/9/20151 The Relational Data Model TCU Database Systems Last update: September 2004 Reference: Elmasri 4 th edition, chapter 5.
Relational Algebra - Chapter (7th ed )
CS 380 Introduction to Database Systems Chapter 7: The Relational Algebra and Relational Calculus.
METU Department of Computer Eng Ceng 302 Introduction to DBMS The Relational Algebra by Pinar Senkul resources: mostly froom Elmasri, Navathe and other.
 Employee (fname, minit, lname, ssn, bdate, address, sex, salary, superssn, dno)  Department (dname, dnumber, mgrssn, mgrstartdate) 
Riyadh Philanthropic Society For Science Prince Sultan College For Woman Dept. of Computer & Information Sciences CS 340 Introduction to Database Systems.
Chapter 6 The Relational Algebra Copyright © 2004 Ramez Elmasri and Shamkant Navathe.
DatabaseIM ISU1 Fundamentals of Database Systems Chapter 6 The Relational Algebra.
1 CS 430 Database Theory Winter 2005 Lecture 4: Relational Model.
CSE314 Database Systems Lecture 3 The Relational Data Model and Relational Database Constraints Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson.
Relational Model E.F. Codd at IBM 1970 Chapter 3 (ed. 7 – Chap. 5)
Review Database Application Development Access Database Development Theory Practice.
Riyadh Philanthropic Society For Science Prince Sultan College For Woman Dept. of Computer & Information Sciences CS 340 Introduction to Database Systems.
1Fundamentals of Database Systems 기본키에 밑줄을 그은 COMPANY 관계 데이타베이스 스키마 FNAMEMINITLNAMESSNBDATEADDRESSSEXSALARYSUPERSSNDNO EMPLOYEE DNAMEDNUMBERMGRSSNMGRSTARTDATE.
Relational Algebra National University of Computer and Emerging Sciences Lecture # 6 June 30,2012.
An introduction to relational database RDB Sept
Chapter 71 The Relational Data Model, Relational Constraints & The Relational Algebra.
Copyright © 2004 Pearson Education, Inc.
The Relational Data Model & Relational Algebra
Database Systems Chapter 6
Chapter (6) The Relational Algebra and Relational Calculus Objectives
4/20/2018.
The SQL Database Grammar
Flat file: A two dimensional array of attributes or data items
Database Design The Relational Model Text Ch5
Chapter (9) ER and EER-to-Relational Mapping, and other Relational Languages Objectives How a relational database schema can be created from a conceptual.
Chapter (9) ER and EER-to-Relational Mapping, and other Relational Languages Objectives How a relational database schema can be created from a conceptual.
376a. Database Design Dept. of Computer Science Vassar College
Chapter 4 The Relational Algebra and Calculus
The Relational Data Model
Chapter (7) The relational Data Model, Relational Constraints, and the Relational Algebra Objectives Describe the basic principals of the relational model.
Joining Tables ضم الجداول وإستخراج مناظر views منها الهدف : 1- استخراج المعلومات من جدولين أو اكثر بالإستفادة من الرابط بينهما وبإستخدام SQL 2- شروط قواعد.
Company Requirements.
The Relational Data Model and Relational Database Constraints
12/7/2018.
Database Systems The Basic (Flat) Relational Model
The Relational Data Model and Relational Database Constraints
Review: Application of Database Systems
Chapter 2: Intro to Relational Model
4/8/2019.
1. Explain the following concepts: (a) superkey (b) key
1.(5) Describe the working process with a database system.
ISC321 Database Systems I Chapter 4: SQL: Data definition, Constraints, and Basic Queries and Updates Fall 2015 Dr. Abdullah Almutairi.
1. Explain the following concepts of the ER data model:
5/12/2019.
Chapter (7) ER-to-Relational Mapping, and other Relational Languages
Copyright © 2004 Pearson Education, Inc.
Presentation transcript:

Outline: Relational Data Model - relation schema, relations - database schema, database state - integrity constraints and updating Relational algebra - select, project, join, cartesian product division - set operations: union, intersection, difference Jan. 2017 Yangjun Chen ACS-3902

dependent Works on employee project department Dept_locations n n 1 1 Jan. 2017 Yangjun Chen ACS-3902

First introduced in 1970 by Ted Codd (IBM) A relation schema R, denoted by R(A1, …, An), is made up of a relation name R and a list of attributes A1, …, An. A relation r(R) is a mathematical relation of degree n on the domains dom(A1), dom(A2), … dom(An), which is a subset of the Cartesian product of the domains that define R: r(R)  (dom(A1)  (dom(A2)  …  (dom(An)) formal terms informal relation table tuple row attribute column header domain data type describing column values Jan. 2017 Yangjun Chen ACS-3902

= {(1, J), (1, D), (2, J), (2, D), (3, J), (3, D)} Cartesian product Emp(SSN, name, sex) 1 2 3 J D m f 1 2 3 J D  = {(1, J), (1, D), (2, J), (2, D), (3, J), (3, D)} Jan. 2017 Yangjun Chen ACS-3902

= {(1, J, m), (1, D, m), (2, J, m), (2, D, m), (3, J, m), (3, D, m), Cartesian product 1 2 3 J D m f   = {(1, J, m), (1, D, m), (2, J, m), (2, D, m), (3, J, m), (3, D, m), (1, J, f), (1, D, f), (2, J, f), (2, D, f), (3, J, f), (3, D, f)} Emp(SSN, name, sex) 1 J m 2 D f Jan. 2017 Yangjun Chen ACS-3902

A domain is a set of atomic values from which values can be drawn Examples - social insurance numbers: set of valid 9-digit social insurance numbers - names: set of names of persons - grade point average: possible values of computed grade point averages; each must be a real number between 0 and 4.5. Jan. 2017 Yangjun Chen ACS-3902

Relation (or Relation State) Domain In many systems one specifies a data type (e.g. integer, date, string(20), …) and writes supporting application code to enforce any specific constraints (e.g. a SIN must be a 9-digit number). Attribute An attribute Ai is a name given to the role a domain plays in a relation schema R. Relation (or Relation State) A relation, or relation state, r of the relation schema R(A1, A2, … An) is a set of n-tuples r={t1, t2, … tm}, where each n-tuple is an ordered list of n values ti=< v1, v2, … vn > (i = 1, …, m). Jan. 2017 Yangjun Chen ACS-3902

EMPLOYEE Name SSN HomePhone Address Relation Schema example EMPLOYEE(Name, SSN, HomePhone, Address, OfficePhone, …) EMPLOYEE Relation example: EMPLOYEE Name SSN HomePhone Address Benjamin Bayer 305-61-2435 373-1616 2918 Bluebonnet Lane ... Katherine Ashly 381-62-1245 375-4409 125 Kirby Road ... Dick Davidson 422-11-2320 null 3452 Elgin Road ... See Figure 6.1 Jan. 2017 Yangjun Chen ACS-3902

Some characteristics of relations no ordering of tuples each value in a tuple is atomic no composite values separate relation tuples for multivalued attributes some attributes may be null no value value missing/unknown a relation is an assertion e.g. an employee entity has a Name, SSN, HomePhone, etc each tuple is a fact or a particular instance some relations store facts about relationships Jan. 2017 Yangjun Chen ACS-3902

instructor teaches course jones z jones Intro to X Z jones Advanced X Intro to X jones smith z Intro to Y smith Intro to Y smith Advanced Y smith Advanced X Advanced Y Jan. 2017 Yangjun Chen ACS-3902

Figure 7.6 - a possible relational database state a relational database schema S is a set of relation schemas S = {R1, R2, ...} and a set of integrity constraints IC. A relational database state DB of S is a set of relation states DB={r(R1), r(R2), ...} such that ... Figure 7.5 - a schema Figure 7.6 - a possible relational database state Figure 7.7 - RI constraints Jan. 2017 Yangjun Chen ACS-3902

fname, minit, lname, ssn, bdate, address, sex, salary, superssn, dno EMPLOYEE fname, minit, lname, ssn, bdate, address, sex, salary, superssn, dno DEPARTMENT Dname, dnumber, mgrssn, mgrstartdate DEPT _LOCATIONS Dnumber, dlocation PROJECT Pname, pnumber, plocation, dnum WORKS ON Essn pno, hours A database schema: DEPENDENT Essn, dependentname, sex, bdate, relationship Jan. 2017 Yangjun Chen ACS-3902

fname, minit, lname, ssn, bdate, address, sex, salary, superssn, dno EMPLOYEE fname, minit, lname, ssn, bdate, address, sex, salary, superssn, dno John B Smith 123489 1965-01-09 731 Fondren M 40000 343488 5 Franklin T Wong 239979 1955-01-10 638 Voss M 50000 343488 5 DEPARTMENT Dname, dnumber, mgrssn, mgrstartdate r(EMPLOYEE) Research 5 343488 1988-05-22 DEPT _LOCATIONS r(DEPARTMENT) Dnumber, dlocation A database state: 5 Houston 6 Stafford r(DEPT_LOCATION) Jan. 2017 Yangjun Chen ACS-3902

Integrity Constraints any database will have some number of constraints that must be applied to ensure correct data (valid states) 1. domain constraints a domain is a restriction on the set of valid values domain constraints specify that the value of each attribute A must be an atomic value from the domain dom(A). 2. key constraints a superkey is any combination of attributes that uniquely identify a tuple: t1[superkey]  t2[superkey]. - Example: <Name, SSN> (in Employee) a key is superkey that has a minimal set of attributes - Example: <SSN> (in Employee) Jan. 2017 Yangjun Chen ACS-3902

Integrity Constraints If a relation schema has more than one key, each of them is called a candidate key. one candidate key is chosen as the primary key (PK) foreign key (FK) is defined as follows: i) Consider two relation schemas R1 and R2; ii) The attributes in FK in R1 have the same domain(s) as the primary key attributes PK in R2; the attributes FK are said to reference or refer to the relation R2; iii) A value of FK in a tuple t1 of the current state r(R1) either occurs as a value of PK for some tuple t2 in the current state r(R2) or is null. In the former case, we have t1[FK] = t2[PK], and we say that the tuple t1 references or refers to the tuple t2. FK Example: FK Employee(SSN, …, Dno) Dept(Dno, …, MGRSSN) Jan. 2017 Yangjun Chen ACS-3902

Integrity Constraints 3. entity integrity no part of a PK can be null 4. referential integrity domain of FK must be same as domain of PK FK must be null or have a value that appears as a PK value 5. semantic integrity other rules that the application domain requires: state constraint: gross salary > net income transition constraint: Widowed can only follow Married; salary of an employee cannot decrease Jan. 2017 Yangjun Chen ACS-3902

fname, minit, lname, ssn, bdate, address, sex, salary, superssn, dno Dname, dnumber, mgrssn, mgrstartdate Dnumber, dlocation Pname, pnumber, plocation, dnum Essn, pno, hours Essn, dependentname, sex, bdate, relationship EMPLOYEE DEPARTMENT DEPT _LOCATIONS WORKS_ON PROJECT DEPENDENT Figure 7-7: reference integrity Jan. 2017 Yangjun Chen ACS-3902

ERD for Chapter 6 database example dependent Dept_locations employee department project ERD for Chapter 6 database example 1 n m Works on Jan. 2017 Yangjun Chen ACS-3902

Updating and constraints insert Insert the following tuple into EMPLOYEE: <‘Cecilia’, ‘F’, ‘Kolonsky’, ‘677678989’, ‘1960-04-05’, ‘6357 Windy Lane, Katy, TX’, F, 40000, null, 4> When inserting, the integrity constraints should be checked: domain, key, entity, referential, semantic integrity update Update the SALARY of the EMPLOYEE tuple with ssn = ‘999887777’ to 30000. When updating, the integrity constraints should be checked: domain, key, entity, referential, semantic integrity Jan. 2017 Yangjun Chen ACS-3902

Updating and constraints delete Delete the WORK_ON tuple with Essn = ‘999887777’ and pno = 10. When deleting, the referential constraint will be checked. - The following deletion is not acceptable: Delete the EMPLOYEE tuple with ssn = ‘999887777’ - reject, cascade, modify Jan. 2017 Yangjun Chen ACS-3902

cascade – a strategy to enforce referential integrity Employee 123456789 ssn ... delete Works-on Essn Pno 123456789 5 ... delete Jan. 2017 Yangjun Chen ACS-3902

cascade – a strategy to enforce referential integrity Employee delete ssn supervisor ... ... 123456789 234589710 null Employee ssn supervisor ... ... 123456789 234589710 null not reasonable delete delete Jan. 2017 Yangjun Chen ACS-3902

Modify – a strategy to enforce referential integrity 123456789 ssn ... Employee Essn Pno 5 delete null This violates the entity constraint. Works-on Jan. 2017 Yangjun Chen ACS-3902

Modify – a strategy to enforce referential integrity Employee 123456789 ssn ... delete Department 123456789 Dno ... 5 chairman Department Dno ... chairman 5 null ... This does not violate the entity constraint. Jan. 2017 Yangjun Chen ACS-3902

Relational Algebra a set of relations select project join division relation specific a set of operations union intersection difference cartesian product set operations Jan. 2017 Yangjun Chen ACS-3902

join (equijoin, natural join, inner, outer) combine multiple relations Relational algebra select horizontal subset project vertical subset join (equijoin, natural join, inner, outer) combine multiple relations cartesian product union, intersection, difference division Jan. 2017 Yangjun Chen ACS-3902

Relational algebra - Select horizontal subset symbol:  boolean condition for row filter e.g. employees earning more than 30,000 salary>30000(Employee) Every column of Employee appears in the result fname minit … salary ... Franklin T … 40000 ... Jennifer S … 43000 ... James E … 55000 ... Jan. 2017 Yangjun Chen ACS-3902

Relational algebra - Project vertical subset symbol:  e.g. names of employees  fname, minit, lname(Employee) fname minit lname John B Sarah Franklin T Wong Alicia J Zalaya Jennifer S Wallace Ramesh K Narayan Joyce A English Ahmad V Jabbar James E Borg Jan. 2017 Yangjun Chen ACS-3902

Relational algebra - Join join or combine tuples from two relations into single tuples symbol: boolean condition specifies the join condition e.g. to report on employees and their dependents Employee ssn=essn Dependent fname minit … essn dependent_name … All attributes of both employee and dependent will appear Jan. 2017 Yangjun Chen ACS-3902

Relational algebra - Join Employee ssn=essn Dependent Essn dependent_name ... 333445555 Alice 333445555 Theodore 333445555 Joy 987654321 Abner 123456789 Michael 123456789 Alice 123456789 Elizabeth fname minit … ssn Franklin T … 333445555 Jennifer S … 987654321 John B … 123456789 Jan. 2017 Yangjun Chen ACS-3902

Employee ssn=essn Dependent fname minit ssn essn Franklin T 333445555 333445555 Alice Franklin T … 333445555 Theodore Franklin T … 333445555 Joy Jennifer S … 987654321 Abner John B … 123456789 Michael John B … 123456789 Alice John B … 123456789 Elizabeth Employee ssn=essn Dependent ... dependent_name Jan. 2017 Yangjun Chen ACS-3902

Relational algebra - Join what is the result of Employee Dependent ? Note there is no join condition This is the Cartesian Product fname minit … essn dependent_name ... If “Employee” contains 7 rows and “Dependent” contains 8 rows, there would be 8 times 7 = 56 rows in the result Jan. 2017 Yangjun Chen ACS-3902

e.g. to report on employees and their dependents R1 Employee Dependent Relational algebra e.g. to report on employees and their dependents R1 Employee Dependent R2  ssn=essn (R1) Result  fname, minit, lname, dependent_name (R2) fname minit lname dependent_name Franklin T Wong Alice Franklin T Wong Theodore Franklin T Wong Joy Jennifer S Wallace Abner John B Smith Michael John B Smith Alice John B Smith Elizabeth Jan. 2017 Yangjun Chen ACS-3902

Relational algebra - Join equijoin - one condition and the = operator natural join - an equijoin with removable of superfluous attribute(s). inner join - only tuples (in one relation) that join with at least one tuple (in the other relation) are included. This is what we have exhibited so far. outer join - full outer join, left outer join, right outer join Jan. 2017 Yangjun Chen ACS-3902

Relational algebra - Natural join natural join - an equijoin with removable of superfluous attribute(s). E.g. to list employees and their dependents: employee * dependent has all attributes of employee, and all attributes of dependent minus essn, in the result if there is ambiguity regarding which attributes are involved, use a list notation like: employee *{ssn, essn} dependent Jan. 2017 Yangjun Chen ACS-3902

join - only matching tuples are in the result Outer Joins join - only matching tuples are in the result left outer join - all tuples of R are in the result regardless ... right outer join - all tuples of S are in the result regardless ... full outer join - all tuples of R and S are in the result regardless ... R S Jan. 2017 Yangjun Chen ACS-3902

Left Outer Joins r1 r2 B1=B2 a1 b1 A B1 a3 b3 a2 b2 C c1 c3 null B2 b4 Jan. 2017 Yangjun Chen ACS-3902

Right Outer Joins r1 r2 r1 r2 a1 b1 A B1 a3 b3 a2 b2 c1 B2 C b4 c4 c3 B1=B2 A B1 C a1 b1 c1 a3 b3 c3 null b4 c4 Jan. 2017 Yangjun Chen ACS-3902

Full Outer Joins r1 r2 r1 r2 a1 b1 A B1 a3 b3 a2 b2 c1 B2 C b4 c4 c3 B1=B2 A B1 C a1 b1 c1 a2 b2 null a3 b3 c3 null b4 c4 Jan. 2017 Yangjun Chen ACS-3902

Result: a list of all employees and also the department they manage Outer Joins Employee Department ssn=mgrssn Dependent ssn=essn Project Works_on pno=pnumber Result: a list of all employees and also the department they manage if they happen to manage a department. Jan. 2017 Yangjun Chen ACS-3902

Set difference, union, intersection A - B A  B A  B A - B A  B A  B A B A B A B Jan. 2017 Yangjun Chen ACS-3902

: : Division T  R S R S T = A B B b1 b2 A a1 b1 a1 a1 b2 a3 a2 b1 a3 Jan. 2017 Yangjun Chen ACS-3902

: Division Query: Retrieve the name of employees who work on all the projects that ‘John Smith’ works on. SMITH  FNAME = ‘John’ and LNAME = ‘Smith’(EMPLOYEE) SMITH_PNOs  PNO(WORK_ON ESSN = SSNSMITH) SSN_PNO  ESSN,PNO(WORK_ON) SSNS(SSN)  SSN_PNO : SMITH_PNOs RESULT  FNAME, LNAME(SSNS * EMPLOYEE) Jan. 2017 Yangjun Chen ACS-3902

fname, minit, lname, ssn, bdate, address, sex, salary, superssn, dno EMPLOYEE fname, minit, lname, ssn, bdate, address, sex, salary, superssn, dno DEPARTMENT Dname, dnumber, mgrssn, mgrstartdate Dnumber, dlocation PROJECT DEPT _LOCATIONS Pname, pnumber, plocation, dnum WORKS_ON Essn, pno, hours DEPENDENT Essn, dependentname, sex, bdate, relationship Jan. 2017 Yangjun Chen ACS-3902

EMPLOYEE WORK_ON ssn fname lname 1 2 3 John Smith Marry Black essn PNo hours 1 ... 1 2 ... 2 3 ... 3 1 ... 3 2 ... 3 ... 3 4 ... Jan. 2017 Yangjun Chen ACS-3902

SMITH  FNAME = ‘John’ and LNAME = ‘Smith’(EMPLOYEE) ssn fname lname 1 John Smith 2 John Smith Jan. 2017 Yangjun Chen ACS-3902

SMITH_PNOs  PNO(WORK_ON ESSN = SSNSMITH) fname lname essn PNo hours Pno 1 1 John Smith ... 1 John Smith 2 ... 2 2 John Smith 3 ... 3 Jan. 2017 Yangjun Chen ACS-3902

SSN_PNO  ESSN,PNO(WORK_ON) 1 1 1 2 2 3 3 1 3 2 3 3 3 4 Jan. 2017 Yangjun Chen ACS-3902

: : SSNS(SSN)  SSN_PNO SMITH_PNOs SSN_PNO SMITH_PNOs SSNS(SSN) essn = 1 1 3 1 1 2 2 2 3 3 3 1 3 2 3 3 3 4 Jan. 2017 Yangjun Chen ACS-3902

RESULT  FNAME, LNAME(SSNS * EMPLOYEE) 3 Marry Black Jan. 2017 Yangjun Chen ACS-3902

: Division The DIVISION operator can be expressed as a sequence of , , and - operations as follows: Z = {A1, …, An, B1, …, Bm}, X = {B1, …, Bm}, Y = Z - X = {A1, …, An}, T1  Y( R) T2  Y((S  T1) - R) T  T1 - T2 : R(Z) S(X) result Jan. 2017 Yangjun Chen ACS-3902