DOC PREVIEW
UCI ICS 184 - Relational Model

This preview shows page 1-2-3-22-23-24-45-46-47 out of 47 pages.

Save
View full document
Premium Document
Do you want full access? Go Premium and unlock all 47 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Relational Model Prof Sharad Mehrotra Information and Computer Science Department University of California at Irvine Chapter 3 and 6 from SKS Chapter 3 in UW Outline Relational model basic modeling concepts for schema specification Mapping ER diagrams to Relational Model Relational Languages relational algebra algebraic basic operators expressions in relational algebra relational calculus logic based will not be covered in class Relational Model Quick Example Ssno Name NULL Street city Account Custid Number Frank 12 Main Champaign 34 1000201 10 799 1200331 Cath y 3 Neil Urbana 45 1200331 1 345 2000312 Bill 45 W Oak Urbana 63 2000312 100 345 balance A relational schema tables and constraints Tables customer account Constraints Key constraints ssno is the key for customer table both accountno and custid are keys for account table Referential Integrity constraints foreign keys The custid attribute in account table takes values from ssno in customer table Null Constraint customer name cannot take null values 3 Relational Model Database schema consists of a set of relation schema a set of constraints over the relation schema Relational Schema name attributes Graphically drawn as table Example employee ssno name salary Recall relation is a subset of cartesian product of sets relation is a set of n tuples where n degree of the relation 4 Attributes With each attribute a domain is specified In relational model attributes are atomic the values are not divisible That is we cannot refer to or directly see a subpart of the value an attribute can take a special null value Null value represents either attributes whose value is not known or do not exist Example of a Relation Diagnosis an example relation table Patient Jim Jane Jerry Joe Disease Schizophrenic Obsessive Comp Manic null null in this case may mean that diagnosis is not complete and disease has not been identified Notice possibility of confusion that null means that the patient has no disease This is one of the reasons why using nulls is not a great idea We will see other reasons as well later 6 Constraints What are they represent the semantics of the domain being modeled restrict the set of possible database states Why do we want to specify the constraints Useful information to application programmers They can write programs to prevent constraints violation constraint acct balance should not fall below 0 dollars programmer writing code for debit application should check at the end if the account gets overdrawn DBMS might enforce specified constraints directly making task of application writer easier If DBMS guarantees that account does not get overdrawn then debit application programmer need not worry about checking for overdrawn account condition 7 Constraints Why specify constraints knowledge of some type of constraints enables us to identify redundancy in schemas and hence specification of constraints helps in database design we will see this later Knowledge of some type of constraints can also help the DBMS in query processing 8 Specifying Constraints in Data Models ER model domain and key constraints over entities participation and cardinality constraints over relationships Relational Model domain constraints entity identity key constraint functional dependencies generalization of key constraints referential integrity inclusion dependencies generalization of referential integrity Domain Constraint In the schema every attribute is declared to have a type integer float date boolean string etc An insertion request can violate the domain constraint DBMS can check if insertion violates domain constraint and reject the insertion 10 Key Constraint Each relation has a primary key Superkey set of attributes such that if two tuples agree on those attributes then they agree on all the attributes of the relation Note the set of all the attributes of a relation is always a superkey Candidate key superkey no subset of which i s a superkey Primary key one of the candidate keys 11 Disallowing Null Values Some fields of a relation are too important to contain null values Example in sales customer salesman date amount saleID we may not want customer to contain a null value 12 Entity Integrity Constraint A primary key must not contain a null value Else it may not be possible to identify some tuples For Example if more than one tuple has a null value in its primary key we may not be able to distinguish them Foreign Key and Referential Integrity Constraint Consider following 2 relation schemas R1 A1 A2 An and R2 B1 B2 Bm Let PK be subset of A1 An be primary key of R1 A set of attributes FK is a foreign key of R2 if attributes in FK have same domain as the attributes in PK For all tuples t2 in R2 there exists a tuple t1in R1 such that t2 FK t1 PK A referential integrity constraint from attributes FK of R2 to R1 means that FK is a foreign that refers to the primary key of R1 14 Example of Referential Integrity student grades student Susan Jane C Semester CS101 1 91 CS101 1 91 grade A B LegalGrades Grade A we will have a referential integrity B constraint saying that C every value of student grades grade D must also be a value of F LegalGrades grade Audit Ex 15 Inclusion Dependencies Generalization of referential integrity constraint Inclusion dependency R1 A1 An R2 B1 Bn means that the values in the first relation R1 refer to the values in the second relation Formally R1 A1 An R2 B1 Bn iff the following holds for all t1 in R1 there exists a t2 in R2 such that t1 A1 An t2 B1 Bn Notice that referential integrity constraint is an inclusion dependency in which B1 Bn is the primary key of R2 16 Example student grade Grade LegalGrade Grade CourseOffering C Courses C Takes S Students S CourseOffering Professor UCEmployee E Data Modification and Integrity Constraints Modification insertion and deletion requests can lead to violations of integrity constraints Key constraint entity identity null value constraint referential integrity inclusion dependencies functional dependencies multivalued dependencies must check for violation at end of each operation and suitably allow or disallow operation Impact of data modification on inclusion dependencies can be sometimes tricky 18 Example Relations CourseOfferings C semester instructor Takes S C semester grade Referential Integrity Constraint Takes C semester CourseOffering C semester Consider canceling a course Delete from courseOfferings where c CS101 AND Semester 2 91 What should happen to tuples in Takes that


View Full Document

UCI ICS 184 - Relational Model

Download Relational Model
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Relational Model and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Relational Model and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?