💾
Welcome to DataGenesis !
  • 🚀 Welcome to the Database Management System Playground! 📊💾
  • Basics of DBMS
    • Database Management System
    • DBMS V/S File System
    • DBMS Architectures
    • Tier 3 Architecture / Three Schema Architecture
  • E-R Data Model
    • Basics of E-R Model
    • Attributes in E-R Model
    • Null Values
    • Strong & Weak Entities
    • Relationship Constraints
    • Recursive Relationships
    • E-R Diagrams
    • Extended E-R Model
  • Relational Model
    • Relational Model
    • Facts About Relational Model
    • Types of Keys in Relational Model
    • Integrity Constraints
    • Anomalies in Relational Model
  • Transform - ER Model to Relational Model
    • Mapping from ER Model to Relational Model
  • SQL - Structured Query Language
    • SQL
    • CRUD Operations
    • Data Types
    • Type of Commands in SQL
    • Working With Commands
    • Data Retrieval Commands
  • Normalisation
    • Functional Dependencies
    • Armstrong's Axioms
    • Multivalued Dependency
    • 1 Normal Form
    • 2 Normal Form
    • 3 Normal Form
    • Boyce-Codd Normal Form (BCNF)
    • 4 Normal Form
    • 5 Normal Form
    • Lossless Decomposition, Lossless Join ,and Dependency Preserving Decomposition, Denormalization
  • Concurrency Control
    • Transactions & Concurrency
    • Scheduling of Transactions
    • Problems & Strategies in Concurrency Control
    • Transaction & ACID Properties
    • How to implement ACID Properties
    • Atomicity Techniques
    • Durability Techniques
    • Implementing Locking in DBMS
    • Concurrency Control Protocols
      • Two Phase Locking
      • Timestamp Ordering
      • Multi Version Concurrency Control Techniques
    • Starvation in DBMS
    • Deadlock in DBMS
    • Log Based Recovery
  • NoSQL & Types of Databases
    • SQL V/S NoSQL
    • Types of Databases
  • DB Optimization
    • File Organization
      • Hash File Organizations
      • B+ Tree File Organization: A Guide to Efficient Data Indexing
      • Cluster File Organization
    • Indexing in DBMS
      • Primary Indexing
      • Clustered Indexing
      • Secondary Indexing
      • Multilevel Indexing
  • Distributed Databases
    • Database Clustering
    • Partitioning and Sharding
    • CAP Theorm
Powered by GitBook
On this page

Was this helpful?

  1. E-R Data Model

Basics of E-R Model

Entity-Relationship (ER) Model: The Entity-Relationship (ER) model is a conceptual data modeling technique used in database design to represent the structure of a database. It provides a way to describe entities, their attributes, and the relationships between entities. The ER model is often represented using Entity-Relationship Diagrams (ERDs).

Entity Set: An entity set is a collection of similar entities. In other words, it's a group of entities that share the same characteristics or attributes. Entities within an entity set represent objects or concepts from the real world that are relevant to the database. For example, in a database for a university, you might have an entity set called "Student" to represent all the students enrolled in the university, and another entity set called "Course" to represent all the courses offered.

Relationships: In the ER model, relationships define how entities are related to each other. Relationships describe the associations or connections between entity sets. There are different types of relationships:

  1. Unary Relationship: Involves a single entity set in a relationship with itself, representing a self-referential connection. Example: "Supervisor" relationship within the "Employee" entity set.

  2. Binary Relationship: Involves two distinct entity sets in a relationship, representing a common and straightforward connection. Example: "Borrow" relationship between "Book" and "Borrower" entity sets in a library database.

  3. Ternary Relationship: Involves three distinct entity sets in a relationship, used for modeling more complex associations or capturing additional information about the relationship itself. Example: A ternary relationship representing course prerequisites involving "Course," "Prerequisite Course," and "Course Offering" entity sets in a university database.

In ER diagrams, relationships are represented by diamond shapes connecting the participating entity sets. The diamond shape contains a verb phrase that describes the nature of the relationship. For example, a relationship between "Student" and "Course" might be labeled "Enrolls In."

The ER model, entity sets, and relationships together provide a clear and intuitive way to represent and plan the structure of a database, making it a valuable tool in database design.

PreviousTier 3 Architecture / Three Schema ArchitectureNextAttributes in E-R Model

Last updated 1 year ago

Was this helpful?