The Relational Model. Why Study the Relational Model?



Similar documents
The Relational Model. Ramakrishnan&Gehrke, Chapter 3 CS4320 1

The Relational Model. Why Study the Relational Model? Relational Database: Definitions. Chapter 3

Lecture 6. SQL, Logical DB Design

The Relational Model. Why Study the Relational Model? Relational Database: Definitions

Outline. Data Modeling. Conceptual Design. ER Model Basics: Entities. ER Model Basics: Relationships. Ternary Relationships. Yanlei Diao UMass Amherst

EECS 647: Introduction to Database Systems

Review Entity-Relationship Diagrams and the Relational Model. Data Models. Review. Why Study the Relational Model? Steps in Database Design

There are five fields or columns, with names and types as shown above.

CS2Bh: Current Technologies. Introduction to XML and Relational Databases. The Relational Model. The relational model

Winter Winter

Database Management Systems. Chapter 1

CS2Bh: Current Technologies. Introduction to XML and Relational Databases. Introduction to Databases. Why databases? Why not use XML?

Review: Participation Constraints

Overview. Introduction to Database Systems. Motivation... Motivation: how do we store lots of data?

Databases Model the Real World. The Entity- Relationship Model. Conceptual Design. Steps in Database Design. ER Model Basics. ER Model Basics (Contd.

Topics. Introduction to Database Management System. What Is a DBMS? DBMS Types

SQL NULL s, Constraints, Triggers

3. Relational Model and Relational Algebra

Data Modeling. Database Systems: The Complete Book Ch ,

SQL: Queries, Programming, Triggers

Example Instances. SQL: Queries, Programming, Triggers. Conceptual Evaluation Strategy. Basic SQL Query. A Note on Range Variables

SQL: Queries, Programming, Triggers

Chapter 5. SQL: Queries, Constraints, Triggers

The core theory of relational databases. Bibliography

Database Security. Chapter 21

Basic Concepts of Database Systems

The Relational Data Model and Relational Database Constraints

Database Systems. Lecture 1: Introduction

COMP 5138 Relational Database Management Systems. Week 5 : Basic SQL. Today s Agenda. Overview. Basic SQL Queries. Joins Queries

Relational model. Relational model - practice. Relational Database Definitions 9/27/11. Relational model. Relational Database: Terminology

CSE 530A Database Management Systems. Introduction. Washington University Fall 2013

Chapter 5 More SQL: Complex Queries, Triggers, Views, and Schema Modification

Oracle Database 10g Express

Schema Evolution in SQL-99 and Commercial (Object-)Relational DBMS

How To Manage Data In A Database System

CS143 Notes: Views & Authorization

How To Create A Table In Sql (Ahem)

SQL DATA DEFINITION: KEY CONSTRAINTS. CS121: Introduction to Relational Database Systems Fall 2015 Lecture 7

SQL Simple Queries. Chapter 3.1 V3.0. Napier University Dr Gordon Russell

A basic create statement for a simple student table would look like the following.

The SQL Query Language. Creating Relations in SQL. Referential Integrity in SQL. Basic SQL Query. Primary and Candidate Keys in SQL

Database Design. Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB

In This Lecture. SQL Data Definition SQL SQL. Notes. Non-Procedural Programming. Database Systems Lecture 5 Natasha Alechina

Ch.5 Database Security. Ch.5 Database Security Review

INFO/CS 330: Applied Database Systems

SQL Tables, Keys, Views, Indexes

Chapter 1: Introduction. Database Management System (DBMS) University Database Example

Relational Database Concepts

CSC 443 Data Base Management Systems. Basic SQL

Relational Database Basics Review

Demystified CONTENTS Acknowledgments xvii Introduction xix CHAPTER 1 Database Fundamentals CHAPTER 2 Exploring Relational Database Components

Physical Database Design Process. Physical Database Design Process. Major Inputs to Physical Database. Components of Physical Database Design

Elena Baralis, Silvia Chiusano Politecnico di Torino. Pag. 1. Active database systems. Triggers. Triggers. Active database systems.

7. Databases and Database Management Systems

2. Conceptual Modeling using the Entity-Relationship Model

ECS 165A: Introduction to Database Systems

1. INTRODUCTION TO RDBMS

Database Design Overview. Conceptual Design ER Model. Entities and Entity Sets. Entity Set Representation. Keys

Geodatabase Programming with SQL

Physical Design. Meeting the needs of the users is the gold standard against which we measure our success in creating a database.

Exercise 1: Relational Model

Databases and BigData

The Entity-Relationship Model

Relational Database Design: FD s & BCNF

2. Basic Relational Data Model

The Relational Data Model: Structure

types, but key declarations and constraints Similar CREATE X commands for other schema ëdrop X name" deletes the created element of beer VARCHARè20è,

HP Quality Center. Upgrade Preparation Guide

- Suresh Khanal. Microsoft Excel Short Questions and Answers 1

Instant SQL Programming

SQL Server An Overview

1 File Processing Systems

Extracting META information from Interbase/Firebird SQL (INFORMATION_SCHEMA)

Computer Security: Principles and Practice

COMP 378 Database Systems Notes for Chapter 7 of Database System Concepts Database Design and the Entity-Relationship Model

Databasesystemer, forår 2005 IT Universitetet i København. Forelæsning 3: Business rules, constraints & triggers. 3. marts 2005

New Security Options in DB2 for z/os Release 9 and 10

In This Lecture. Security and Integrity. Database Security. DBMS Security Support. Privileges in SQL. Permissions and Privilege.

Chapter 6: Integrity Constraints

Overview of Database Management Systems

DBMS Questions. 3.) For which two constraints are indexes created when the constraint is added?

BCA. Database Management System

DATABASE MANAGEMENT SYSTEMS. Question Bank:

Security and Authorization. Introduction to DB Security. Access Controls. Chapter 21

Testing of the data access layer and the database itself

Introduction to Databases

The Structured Query Language. De facto standard used to interact with relational DB management systems Two major branches

DataBase Management Systems Lecture Notes

Database Design and Programming

Procedural Extension to SQL using Triggers. SS Chung

Part A: Data Definition Language (DDL) Schema and Catalog CREAT TABLE. Referential Triggered Actions. CSC 742 Database Management Systems

Normalization. Functional Dependence. Normalization. Normalization. GIS Applications. Spring 2011

SQL Programming. CS145 Lecture Notes #10. Motivation. Oracle PL/SQL. Basics. Example schema:

6 CHAPTER. Relational Database Management Systems and SQL Chapter Objectives In this chapter you will learn the following:

Query-by-Example (QBE)

Introduction to Computing. Lectured by: Dr. Pham Tran Vu

Maintaining Stored Procedures in Database Application

5.1 Database Schema Schema Generation in SQL

Week 1 Part 1: An Introduction to Database Systems. Databases and DBMSs. Why Use a DBMS? Why Study Databases??

IT2304: Database Systems 1 (DBS 1)

Transcription:

The Relational Model Chapter 3 Instructor: Vladimir Zadorozhny vladimir@sis.pitt.edu Information Science Program School of Information Sciences, University of Pittsburgh 1 Why Study the Relational Model? v Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase, etc. v Legacy systems in older models E.G., IBM s IMS v Recent competitor: object-oriented model ObjectStore, Versant, Ontos A synthesis emerging: object-relational model Informix Universal Server, UniSQL, O2, Oracle, DB2 2

Relational Database: Definitions v Relational database: a set of relations v Relation: made up of 2 parts: Instance : a table, with rows and columns. #Rows = cardinality, #fields = degree / arity. Schema : specifies name of relation, plus name and type of each column. E.G. Students(sid: string, name: string, login: string, age: integer, gpa: real). v Can think of a relation as a set of rows or tuples (i.e., all rows are distinct). 3 Example Instance of Students Relation sid name login age gpa 53666 Jones jones@cs 18 3.4 53688 Smith smith@eecs 18 3.2 53650 Smith smith@math 19 3.8 v Cardinality = 3, degree = 5, all rows distinct v Do all columns in a relation instance have to be distinct? 4

Relational Query Languages v A major strength of the relational model: supports simple, powerful querying of data. v Queries can be written intuitively, and the DBMS is responsible for efficient evaluation. The key: precise semantics for relational queries. Allows the optimizer to extensively re-order operations, and still ensure that the answer does not change. 5 The SQL Query Language v Developed by IBM (system R) in the 1970s v Need for a standard since it is used by many vendors v Standards: SQL-86 SQL-89 (minor revision) SQL-92 (major revision) SQL-99 (major extensions, current standard) 6

The SQL Query Language v To find all 18 year old students, we can write: SELECT * FROM Students S WHERE S.age=18 sid name login age gpa 53666 Jones jones@cs 18 3.4 53688 Smith smith@ee 18 3.2 To find just names and logins, replace the first line: SELECT S.name, S.login 7 Querying Multiple Relations v What does the following query compute? SELECT S.name, E.cid FROM Students S, Enrolled E WHERE S.sid=E.sid AND E.grade= A Students: sid name login age gpa 53666 Jones jones@cs 18 3.4 53688 Smith smith@ee 18 3.2 Enrolled: sid cid grade 53831 Carnatic101 C 53831 Reggae203 B 53650 Topology112 A 53666 History105 B Result: S.name Smith E.cid Topology112 8

Creating Relations in SQL v Creates the Students relation. Observe that the type (domain) of each field is specified, and enforced by the DBMS whenever tuples are added or modified. v As another example, the Enrolled table holds information about courses that students take. CREATE TABLE Students (sid: CHAR(20), name: CHAR(20), login: CHAR(10), age: INTEGER, gpa: REAL) CREATE TABLE Enrolled (sid: CHAR(20), cid: CHAR(20), grade: CHAR(2)) 9 Destroying and Altering Relations DROP TABLE Students v Destroys the relation Students. The schema information and the tuples are deleted. ALTER TABLE Students ADD COLUMN firstyear: integer v The schema of Students is altered by adding a new field; every tuple in the current instance is extended with a null value in the new field. 10

Adding and Deleting Tuples v Can insert a single tuple using: INSERT INTO Students (sid, name, login, age, gpa) VALUES (53688, Smith, smith@ee, 18, 3.2) v Can delete all tuples satisfying some condition (e.g., name = Smith): DELETE FROM Students S WHERE S.name = Smith Powerful variants of these commands are available; more later! 11 Modifying Tuples v Increment the age and decrement the gpa of the student with sid 5368: UPDATE Students S SET S.age = S.age + 1 and S.gpa = S.gpa - 1 WHERE S.sid = 5368 v Give a 1% increase to the gpa of all students with the gpa more or equal to 3.3: UPDATE Students S SET S.gpa = S.gpa*1.01 WHERE S.gpa >= 3.3 12

Integrity Constraints (ICs) v IC: condition that must be true for any instance of the database; e.g., domain constraints. ICs are specified when schema is defined. ICs are checked when relations are modified. v A legal instance of a relation is one that satisfies all specified ICs. DBMS should not allow illegal instances. v If the DBMS checks ICs, stored data is more faithful to real-world meaning. Avoids data entry errors, too! 13 Primary Key Constraints v A set of fields is a key for a relation if : 1. No two distinct tuples can have same values in all key fields, and 2. This is not true for any subset of the key. Part 2 false? A superkey. If there s >1 key for a relation, one of the keys is chosen (by DBA) to be the primary key. v E.g., sid is a key for Students. (What about name?) The set {sid, gpa} is a superkey. 14

Primary and Candidate Keys in SQL v Possibly many candidate keys (specified using UNIQUE), one of which is chosen as the primary key. v For a given student and course, there is a single grade. vs. Students can take only one course, and receive a single grade for that course; further, no two students in a course receive the same grade. v Used carelessly, an IC can prevent the storage of database instances that arise in practice! CREATE TABLE Enrolled (sid CHAR(20) cid CHAR(20), grade CHAR(2), PRIMARY KEY (sid,cid) ) CREATE TABLE Enrolled (sid CHAR(20) cid CHAR(20), grade CHAR(2), PRIMARY KEY (sid), UNIQUE (cid, grade) ) 15 Foreign Keys, Referential Integrity v Foreign key : Set of fields in one relation that is used to `refer to a tuple in another relation. (Must correspond to primary key of the second relation.) Like a `logical pointer. v E.g. sid is a foreign key referring to Students: Enrolled(sid: string, cid: string, grade: string) If all foreign key constraints are enforced, referential integrity is achieved, i.e., no dangling references. Can you name a data model w/o referential integrity? Links in HTML! 16

Foreign Keys in SQL v Only students listed in the Students relation should be allowed to enroll for courses. CREATE TABLE Enrolled (sid CHAR(20), cid CHAR(20), grade CHAR(2), PRIMARY KEY (sid,cid), FOREIGN KEY (sid) REFERENCES Students ) Enrolled sid cid grade 53666 Carnatic101 C 53666 Reggae203 B 53650 Topology112 A 53666 History105 B Students sid name login age gpa 53666 Jones jones@cs 18 3.4 53688 Smith smith@eecs 18 3.2 53650 Smith smith@math 19 3.8 17 Enforcing Referential Integrity v Consider Students and Enrolled; sid in Enrolled is a foreign key that references Students. v What should be done if an Enrolled tuple with a non-existent student id is inserted? (Reject it!) v What should be done if a Students tuple is deleted? Also delete all Enrolled tuples that refer to it. Disallow deletion of a Students tuple that is referred to. Set sid in Enrolled tuples that refer to it to a default sid. (In SQL, also: Set sid in Enrolled tuples that refer to it to a special value null, denoting `unknown or `inapplicable.) v Similar if primary key of Students tuple is updated. 18

Referential Integrity in SQL v SQL/92 and SQL:1999 support all 4 options on deletes and updates. Default is NO ACTION (delete/update is rejected) CASCADE (also delete all tuples that refer to deleted tuple) SET NULL / SET DEFAULT (sets foreign key value of referencing tuple) CREATE TABLE Enrolled (sid CHAR(20), cid CHAR(20), grade CHAR(2), PRIMARY KEY (sid,cid), FOREIGN KEY (sid) REFERENCES Students ON DELETE CASCADE ON UPDATE SET DEFAULT ) 19 Where do ICs Come From? v ICs are based upon the semantics of the realworld enterprise that is being described in the database relations. v We can check a database instance to see if an IC is violated, but we can NEVER infer that an IC is true by looking at an instance. An IC is a statement about all possible instances! From example, we know name is not a key, but the assertion that sid is a key is given to us. v Key and foreign key ICs are the most common; more general ICs supported too. 20

Views v A view is just a relation, but we store a definition, rather than a set of tuples. CREATE VIEW YoungActiveStudents (name, grade) AS SELECT S.name, E.grade FROM Students S, Enrolled E WHERE S.sid = E.sid and S.age<21 v Views can be dropped using the DROP VIEW command. How to handle DROP TABLE if there s a view on the table? DROP TABLE command has options to let the user specify this. 21 Views and Security v Views can be used to present necessary information (or a summary), while hiding details in underlying relation(s). Given YoungStudents, but not Students or Enrolled, we can find students s who have are enrolled, but not the cid s of the courses they are enrolled in. 22

Relational Model: Summary v A tabular representation of data. v Simple and intuitive, currently the most widely used. v Integrity constraints can be specified by the DBA, based on application semantics. DBMS checks for violations. Two important ICs: primary and foreign keys In addition, we always have domain constraints. v Powerful and natural query languages exist. 23