SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Understanding Relational Data Model: From E/R Diagrams to Relation Tables

baby avatar
baby
16 diapositives · 329 Views · Sep 04, 2014

This document explores the transformation from Entity-Relationship (E/R) diagrams to relational tables in database design. It covers foundational concepts such as relations, schemas, and attributes, presenting practical examples like cars and manufacturers. Key relationships and guidelines for combining relations are discussed, along with the risks of redundancy in many-to-many relationships. Additionally, it addresses weak entity sets and various subclass approaches, including object-oriented designs and the use of NULL attributes. The material emphasizes the simplicity and utility of the relational model in structuring data effectively.

#understanding relational data model: from e/r diagrams to relation tables #understanding relational data model: from e/r diagrams to relation tables ppt #powerpoint #presentation
Understanding Relational Data Model: From E/R Diagrams to Relation Tables - slide 1
01 / 16Understanding Relational Data Model: From E/R Diagrams to Relation Tables
1 / 17

Télécharger la présentation

Understanding Relational Data Model: From E/R Diagrams to Relation Tables
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. The Relational Data Model Tables Schemas Conversion from E/R to Relations

  2. Attributes (column headers) Tuples (rows) A Relation is a Table name manf Corvette G.M. Maxima Nissan cars

  3. Schemas • Relation schema = relation name and attribute list. • Optionally: types of attributes. • Example: cars(name, manf) or cars(name: string, manf: string) • Database = collection of relations. • Database schema = set of all relation schemas in the database.

  4. Why Relations? • Very simple model. • Often matches how we think about data. • Abstract model that underlies SQL, the most important database language today.

  5. From E/R Diagrams to Relations • Entity set -> relation. • Attributes -> attributes. • Relationships -> relations whose attributes are only: • The keys of the connected entity sets. • Attributes of the relationship itself.

  6. Entity Set -> Relation Relation: cars(model, manf) model manf cars

  7. Likes husband 2 1 Favorite Mustangdies Likes(driver, car) Favorite(driver, car) wife Mustangdies(name1, name2) Married Married(husband, wife) Relationship -> Relation name name addr manf drivers cars

  8. Combining Relations • OK to combine into one relation: • The relation for an entity-set E • The relations for many-one relationships of which E is the “many.” • Example: drivers(name, addr) and Favorite(driver, car) combine to make driver1(name, addr, favcar).

  9. Redundancy Risk with Many-Many Relationships • Combining drivers with Likes would be a mistake. It leads to redundancy, as: name addr car Sally 123 Maple Mustang Sally 123 Maple Maxima

  10. Handling Weak Entity Sets • Relation for a weak entity set must include attributes for its complete key (including those belonging to other entity sets), as well as its own, nonkey attributes. • A supporting relationship is redundant and yields no relation (unless it has attributes).

  11. Must be the same At becomes part of Logins Example name name Logins At Hosts location billTo Hosts(hostName, location) Logins(loginName, hostName, billTo) At(loginName, hostName, hostName2)

  12. Subclasses: Three Approaches • Object-oriented: One relation per subset of subclasses, with all relevant attributes. • Use nulls: One relation; entities have NULL in attributes that don’t belong to them. • E/R style: One relation for each subclass: • Key attribute(s). • Attributes of that subclass.

  13. Example cars model manf isa Sports Car RLR

  14. Object-Oriented name manf Mustang Nissan cars name manf RLR Corvette G.M. None Sports Good for queries like “find the RLR of Sports Car made by G.M..”

  15. E/R Style name manf Mustang Nissan Corvette G.M. Cars name RLR Corvette none Sports Cars Good for queries like “find all cars (including Sports Cars) made by G.M..”

  16. Using Nulls name manf RLR Mustang Nissan NULL Corvette G.M. none cars Saves space unless there are lots of attributes that are usually NULL.