Announcements. Database Design. Database Design. Database Design Process. Entity / Relationship Diagrams. Introduction to Data Management CSE 344

Transcription

1 Announcements Introduction to Data Management CSE 344 HW5 due this Friday Please note minor up to the instructions WQ6 due next Wednesday Lecture 17: E/R Diagrams and Constraints 1 2 Database Design What it is: Starting from scratch, design the database schema: relation, attributes, keys, foreign keys, constraints etc Why it s hard The database will be in operation for a very long time (years). Updating the schema while in production is very expensive (why?) Database Design Consider issues such as: What entities to model How entities are related What constraints exist in the domain Several formalisms exists We discuss E/R diagrams Reading: Sec Database Design Process Entity / Relationship Diagrams Conceptual Model: Relational Model: Tables + constraints And also functional dep. product company Entity set = a class An entity = an object Attribute city Normalization: Eliminates anomalies Conceptual Schema Relationship Physical storage details Physical Schema 5 6 1

2 CEO Keys in E/R Diagrams Every entity set must have a key buys employs ssn 7 8 What is a Relation? Multiplicity of E/R Relations A mathematical definition: if A, B are sets, then a relation R is a subset of A B A={1,2,3}, B={a,b,c,d}, A B = {(1,a),(1,b),..., (3,d)} R = {(1,a), (1,c), (3,b)} A= 1 2 a b c 3 B= is a subset of : d 9 one-one: many-one many-many a b c d a b c d a b c d 10 CEO Multi-way Relationships How do we model a purchase relationship between buyers, products and stores? buys What does this say? employs Can still model as a mathematical set (Q. how?) ssn 11 A. As a set of triples 12 2

3 Arrows in Multiway Relationships Q: What does the arrow mean? Arrows in Multiway Relationships Q: What does the arrow mean? A: A given person buys a given product from at most one store [Arrow pointing to E means that if we select one entity from each of the other entity sets in the relationship, those entities are related to at most one entity in E] 13 A: A given person buys a given product from at most one store AND every store sells to every person at most one product 14 Converting Multi-way Relationships to Binary Converting Multi-way Relationships to Binary Of Of Of Of BuyerOf BuyerOf Arrows go in which direction? 15 Make sure you understand why! 16 What s wrong? 3. Design Principles Design Principles: What s Wrong? Country President Moral: be faithful to the specifications of the app! personaddr personname Moral: pick the right kind of entities

4 Design Principles: What s Wrong? From E/R Diagrams to Relational Schema Dates Entity set à relation Relationship à relation Moral: don t complicate life more than it already is Entity Set to Relation N-N Relationships to Relations prod-id category prod-id cust-id (prod-id, category, ) prod-id category Pokemn19 Toy Orders Shipment Shipping-Co Represent this in relations 22 N-N Relationships to Relations N-1 Relationships to Relations prod-id cust-id prod-id cust-id Orders Shipment Shipping-Co Orders Shipment Shipping-Co Orders(prod-ID,cust-ID, ) Shipment(prod-ID,cust-ID,, ) Shipping-Co(, ) prod-id cust-id 55 Joe12 UPS 4/10/ Joe12 FEDEX 4/9/2011 Represent this in relations 24 4

5 N-1 Relationships to Relations prod-id cust-id Multi-way Relationships to Relations prod-id Orders Shipment Orders(prod-ID,cust-ID, 1,, 2) Shipping-Co(, ) Shipping-Co Remember: no separate relations for many-one relationship 25 ssn (prod-id, ssn, ) 26 Modeling Subclasses Subclasses category Some objects in a class may be special define a new class better: define a subclass s Software products Educational products So --- we define subclasses in E/R Software Educational 27 platforms Age Group Subclasses to Relations Software platforms category Educational Other ways to convert are possible Sw. Age Group Name Price Category 99 gadget 49 photo Toy 39 gadget Name Ed. Name platforms unix Age Group toddler Toy retired 29 Modeling Union Types with Subclasses FurniturePiece Say: each piece of furniture is owned either by a person or by a company 30 5

6 Modeling Union Types with Subclasses Say: each piece of furniture is owned either by a person or by a company Solution 1. Acceptable but imperfect (What s wrong?) Modeling Union Types with Subclasses Solution 2: better, more laborious Owner FurniturePiece ownedby ownedbycomp. 31 ownedby FurniturePiece 32 Weak Entity Sets A What Are the Keys of R? Entity sets are weak when their key comes from other classes to which they are related. B R H S Team affiliation University sport number T C W U V Team(sport, number, universityname) University() 33 V D E Q F L G Z 34 K What good schemas? Integrity Constraints Motivation An integrity constraint is a condition specified on a database schema that restricts the data that can be stored in an instance of the database. ICs help prevent entry of incorrect information How? DBMS enforces integrity constraints Allows only legal database instances (i.e., those that satisfy all constraints) to exist Ensures that all necessary checks are always performed and avoids duplicating the verification logic in each application

7 Constraints in E/R Diagrams Keys in E/R Diagrams Finding constraints is part of the modeling process. Commonly used constraints: Underline: category Keys: social security number uniquely identifies a person. Single-value constraints: a person can have only one father. Referential integrity constraints: if you work for a company, it must exist in the database. No formal way to specify multiple keys in E/R diagrams Other constraints: peoples ages are between 0 and ssn 38 Single Value Constraints Referential Integrity Constraints vs. Each product made by at most one company. Some products made by no company 39 Each product made by exactly one company. 40 Other Constraints Constraints in SQL <100 Constraints in SQL: Keys, foreign keys Attribute-level constraints Tuple-level constraints Global constraints: assertions simplest Most complex Q: What does this mean? A: A entity cannot be connected by relationship to more than 99 entities The more complex the constraint, the harder it is to check and to enforce

8 (, category) Key Constraints CREATE TABLE ( CHAR(30) PRIMARY KEY, category VARCHAR(20)) Keys with Multiple Attributes (, category, ) CREATE TABLE ( CHAR(30), INT, PRIMARY KEY (, category)) OR: CREATE TABLE ( CHAR(30), PRIMARY KEY ()) Name Category Price Gadget 10 Photo 20 Photo 30 Gadget Other Keys Foreign Key Constraints CREATE TABLE ( productid CHAR(10), CHAR(30), INT, PRIMARY KEY (productid), UNIQUE (, category)) There is at most one PRIMARY KEY; there can be many UNIQUE CREATE TABLE ( prodname CHAR(30) REFERENCES (), DATETIME) prodname is a foreign key to () must be a key in Referential integrity constraints May write just if is PK Foreign Key Constraints Example with multi-attribute primary key CREATE TABLE ( prodname CHAR(30), DATETIME, FOREIGN KEY (prodname, category) REFERENCES (, category) (, category) must be a KEY in Name OneClick What happens when data changes? Types of ups: In : insert/up In : delete/up Category gadget Photo Photo ProdName Wiz Ritz Wiz

9 What happens when data changes? SQL has three policies for maintaining referential integrity: NO ACTION reject violating modifications (default) CASCADE after delete/up do delete/up SET NULL set foreign-key field to NULL SET DEFAULT set foreign-key field to default value need to be declared with column, e.g., CREATE TABLE (pid INT DEFAULT 42) 49 Maintaining Referential Integrity CREATE TABLE ( prodname CHAR(30), DATETIME, FOREIGN KEY (prodname, category) REFERENCES (, category) ON UPDATE CASCADE ON DELETE SET NULL ) Name OneClick Category gadget Photo Photo ProdName Snap EasyShoot Category 50 Constraints on Attributes and Tuples Constraints on attributes: NOT NULL -- obvious meaning... CHECK condition -- any condition! Constraints on tuples CHECK condition Constraints on Attributes and Tuples CREATE TABLE R ( A int NOT NULL, B int CHECK (B > 50 and B < 100), C varchar(20), D int, CHECK (C >= 'd' or D > 0)) Constraints on Attributes and Tuples CREATE TABLE ( productid CHAR(10), CHAR(30), INT CHECK ( > 0), PRIMARY KEY (productid), UNIQUE (, category)) Constraints on Attributes and Tuples What does this constraint do? What is the difference from CREATE TABLE ( Foreign-Key? prodname CHAR(30) CHECK (prodname IN (SELECT. FROM ), DATETIME NOT NULL)

10 General Assertions CREATE ASSERTION myassert CHECK (NOT EXISTS( SELECT. FROM, WHERE. =.prodname GROUP BY. HAVING count(*) > 200) ) But most DBMSs do not implement assertions Because it is hard to support them efficiently Instead, they provide triggers 55 10