liveBook · Manning

Transitive dependency

A dependency is transitive when one item depends on another indirectly through an intermediate item rather than directly.

How 3 Manning books explain it

100 SQL Server Mistakes and How to Avoid Them

A transitive dependency occurs when a non-key attribute depends on another non-key attribute rather than directly on the key.

How it is used
Uses 3NF to identify attributes determined by nonprime attributes and separate them into related relations.
How deep it goes
Defines nontransitive dependence and demonstrates several relation splits, without formal dependency notation or algorithms.
Examples
Uses product type descriptions, salespeople, sales areas, customers, and customer contacts as dependency examples.
What you can do after
Apply it by decomposing relations and reconnecting them through foreign keys when nonprime attributes identify other attributes.

Read how 100 SQL Server Mistakes and How to Avoid Them explains transitive dependency →

Grokking Relational Database Design

A transitive dependency is a functional dependency in which a nonkey attribute depends on another nonkey attribute that depends on a key.

How it is used
Uses transitive dependencies to check database tables against 3NF and BCNF requirements.
How deep it goes
Defines the dependency chain, explains its anomalies, and demonstrates decomposition with foreign keys; it stops short of later normal forms.
Examples
Uses employee-department data and a purchase-payment_method-user relationship to expose direct and indirect dependencies.
What you can do after
Diagnose transitive dependencies and redesign affected tables with separate entities and foreign-key links.

Read how Grokking Relational Database Design explains transitive dependency →

Microservices Patterns, Second Edition

A dependency introduced indirectly through another dependency rather than declared directly by the application.

How it is used
Explains how indirect dependencies complicate technology-stack compatibility and propagate build-time coupling.
How deep it goes
Traces an indirect Gradle dependency into downstream tests and discusses version compatibility, without prescribing resolution steps.
Examples
Uses Java and Maven version conflicts, a Terraform provider blocking a Kubernetes upgrade, and Gradle project dependencies.
What you can do after
Diagnose build impact by tracing an indirect Gradle project dependency to downstream recompilation and tests.

Read how Microservices Patterns, Second Edition explains transitive dependency →

Also covered in

Related concepts

Questions about transitive dependency

What is transitive dependency?

A dependency is transitive when one item depends on another indirectly through an intermediate item rather than directly.

Which Manning books explain transitive dependency?

100 SQL Server Mistakes and How to Avoid Them, Grokking Relational Database Design and Microservices Patterns, Second Edition.

What is the difference between transitive dependency and Go compiler?

A dependency is transitive when one item depends on another indirectly through an intermediate item rather than directly. The Go compiler is the program that checks Go source code and translates it into executable machine code or an intermediate representation.

What is transitive dependency a kind of?

Transitive dependency is a kind of dependency. A dependency is a component, resource, or prerequisite that another software component or activity relies on to function, build, or proceed.

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.