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). Can think of a relation as a set of rows or tuples (i.e., all rows are distinct).
Creating Relations in SQL Creates the Students CREATE TABLE Students relation. Observe that the (sid: CHAR(20), type (domain) of each field name: CHAR(20), login: CHAR(10), is specified, and enforced by age: INTEGER, the DBMS whenever tuples gpa: REAL) are added or modified. As another example, the CREATE TABLE Enrolled Enrolled table holds (sid: CHAR(20), information about courses cid: CHAR(20), that students take. grade: CHAR(2))
new field; every tuple in the current instance is extended with a null value in the new field. 1/28/2008 USC - CSCI585 - Spring 2008 - Farnoush Banaei-Kashani 7 Adding and Deleting Tuples Can insert a single tuple using: INSERT INTO Students (sid, name, login, age, gpa) VALUES (53688, ‘Smith’, ‘smith@ee’, 18, 3.2)
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!
1/28/2008 USC - CSCI585 - Spring 2008 - Farnoush Banaei-Kashani 8 Integrity Constraints (ICs) 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. A legal instance of a relation is one that satisfies all specified ICs. DBMS should not allow illegal instances. If the DBMS checks ICs, stored data is more faithful to real-world meaning. Avoids data entry errors, too!
world enterprise that is being described in the database relations. 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.
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. E.g., sid is a key for Students. (What about name?) The set {sid, gpa} is a superkey.
Primary and Candidate Keys in SQL Possibly many candidate keys (specified using UNIQUE), one of which is chosen as the primary key. CREATE TABLE Enrolled “For a given student and course, (sid CHAR(20) there is a single grade.” cid CHAR(20), grade CHAR(2), vs. PRIMARY KEY (sid,cid) ) CREATE TABLE Enrolled “Students can take only one (sid CHAR(20) course, and receive a single grade cid CHAR(20), for that course; further, no two grade CHAR(2), students in a course receive the PRIMARY KEY (sid), same grade.” UNIQUE (cid, grade) ) 1/28/2008 USC - CSCI585 - Spring 2008 - Farnoush Banaei-Kashani 12 Foreign Keys, Referential Integrity
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’. 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!
Foreign Keys in SQL 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 Students 53666 Carnatic101 C sid name login age gpa 53666 Reggae203 B 53666 Jones jones@cs 18 3.4 53650 Topology112 A 53688 Smith smith@eecs 18 3.2 53666 History105 B 53650 Smith smith@math 19 3.8
Enforcing Referential Integrity Consider Students and Enrolled; sid in Enrolled is a foreign key that references Students. What should be done if an Enrolled tuple with a non- existent student id is inserted? (Reject it!) What should be done if a Students tuple is deleted? Also delete all Enrolled tuples that refer to it (CASCADE). Disallow deletion of a Students tuple that is referred to (NO ACTION). Set sid in Enrolled tuples that refer to it to a default sid (SET DEFAULT). In SQL, also: Set sid in Enrolled tuples that refer to it to a special value null, denoting `unknown’ or `inapplicable’ (SET NULL). Similar if primary key of Students tuple is updated.
support all 4 options on (sid CHAR(20), deletes and updates. cid CHAR(20), Default is NO ACTION grade CHAR(2), (delete/update is rejected) PRIMARY KEY (sid,cid), CASCADE (also delete FOREIGN KEY (sid) all tuples that refer to REFERENCES Students deleted tuple) ON DELETE CASCADE ON UPDATE SET DEFAULT ) SET NULL / SET DEFAULT (sets foreign key value of referencing tuple)
Simple and intuitive, currently the most widely used. 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. Powerful and natural query languages exist. There are rules to translate ER to relational model