CHAPTER4-High Level Database Models.pptVIP

Chapter 4: High-Level Database Models E/R Diagrams Weak Entity Sets Converting E/R Diagrams to Relations Purpose of E/R Model The E/R model allows us to sketch database schema designs. Includes some constraints, but not operations. Designs are pictures called entity-relationship diagrams. Later: convert E/R designs to relational DB designs. Framework for E/R Design is a serious business. The “boss” knows they want a database, but they don’t know what they want in it. Sketching the key components is an efficient way to develop a working database. 4.1 Entity-Relationship Model Entity = “thing” or object. Entity set = collection of similar entities. Similar to a class in object-oriented languages. Attribute = property of (the entities of) an entity set. Attributes are simple values, e.g. integers or character strings, not structs, sets, etc. E/R Diagrams In an entity-relationship diagram: Entity set = rectangle. Attribute = oval, with a line to the rectangle representing its entity set. Example: Entity set Beers has two attributes, name and manf (manufacturer). Each Beers entity has values for these two attributes, e.g. (Bud, Anheuser-Busch) Relationships A relationship connects two or more entity sets. It is represented by a diamond, with lines to each of the entity sets involved. Example: Relationships Relationship Set The current “value” of an entity set is the set of entities that belong to it. Example: the set of all bars in our database. The “value” of a relationship is a relationship set, a set of tuples with one component for each related entity set. Example: Relationship Set For the relationship Sells, we might have a relationship set like: Multiway Relationships Sometimes, we need a relationship that connects more than two entity sets. Suppose that drinkers will only drink certain beers at certain bars. Our three binary relationships Likes, Sells, and Frequents do not allow us to make this distinction. But a 3-way relationship would. Example: 3-Way Rela