Entity-relationship diagram
An entity-relationship diagram is a visual model representing data entities, their attributes, relationships, and applicable constraints.
Grokking Relational Database Design
An entity-relationship diagram is a visual model showing entities, their attributes, and the relationships between them, including relationship cardinalities.
- How it is used
- Uses visual data modeling to turn database requirements into a structured schema and relationship rules.
- How deep it goes
- Develops entities, relationships, cardinalities, junction tables, and weak entities, but defers normalization and detailed attributes.
- Examples
- Uses an online store with users, purchases, products, reviews, payment methods, and a purchase-product junction table.
- What you can do after
- Build it from scratch by translating requirements into entities, connections, cardinalities, and relationship-supporting tables.
Read how Grokking Relational Database Design explains entity-relationship diagram →
Graph Neural Networks in Action
An entity-relationship diagram is a visual model showing entities, relationships, attributes, and constraints in a data or graph design.
- How it is used
- Frames graph entities, relationships, and constraints before designing datasets and experimenting with GNN pipeline rules.
- How deep it goes
- Defines the diagram and relates it to schemas, but defers detailed graph-data-model treatment to another reference.
- Examples
- Shows relationship nomenclature, a conceptual schema, and schemas containing one, two, or three node and edge types.
- What you can do after
- Build explicit graph structures and rules that support parameterized GNN experiments.
Read how Graph Neural Networks in Action explains entity-relationship diagram →
100 SQL Server Mistakes and How to Avoid Them
An entity relationship diagram is a diagram that represents data entities, their attributes, and the relationships between them.
- How it is used
- Documents and validates database schemas by making entities, attributes, keys, relationships, and selected data types explicit.
- How deep it goes
- Explains diagram contents and validation purpose, but stops short of prescribing a complete notation or diagramming procedure.
- Examples
- Uses an Employees ERD annotated with column expectations and SQL Server data-type choices such as SMALLINT and BIT.
- What you can do after
- Evaluate schema structure, validate normalization, and document key relationships and column definitions.
Read how 100 SQL Server Mistakes and How to Avoid Them explains entity-relationship diagram →
Data-Oriented Programming: Reduce software complexity
A data entity diagram is a visual model that represents data entities and distinguishes association and composition relationships between them.
- How it is used
- Separates data modeling from code while making entity relationships explicit.
- How deep it goes
- Refines entities, fields, relationship kinds, identifiers, and indexes, but leaves broader representation details for later design.
- Examples
- Uses a library system containing books, authors, catalogs, users, members, and librarians.
- What you can do after
- Build it from scratch by grouping entities, classifying relationships, choosing identifiers, and defining lookup indexes.
Related concepts
- data modelproduced by · A data model is a structured representation of data that defines its entities, attributes, relationships, and applicable constraints.
- language modelkind of · A language model is a computational model that represents patterns in linguistic tokens to estimate sequence probabilities and predict or generate language from context.
- positional collectionhas part · A positional collection is an ordered collection whose elements are accessed by their positions.
- schemauses · A data schema is a formal specification of the structure, fields, types, relationships, and constraints of data.
- indexinghas part · Indexing is the organization or use of positions, keys, or lookup structures to identify and retrieve selected data or elements.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.