From af5af8df88acdc40f22f342a7893ca26f5e66651 Mon Sep 17 00:00:00 2001 From: Dan Borstelmann Date: Sun, 12 Apr 2020 18:05:46 -0700 Subject: [PATCH] Update 02-why-prisma.mdx --- content/02-understand-prisma/02-why-prisma.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/02-understand-prisma/02-why-prisma.mdx b/content/02-understand-prisma/02-why-prisma.mdx index 04798b79b7..1b842611ab 100644 --- a/content/02-understand-prisma/02-why-prisma.mdx +++ b/content/02-understand-prisma/02-why-prisma.mdx @@ -52,7 +52,7 @@ As an application developer, the mental model you have for your data is that of The divide between these two different representations of data is often referred to as the [object-relational impedance mismatch](https://en.wikipedia.org/wiki/Object-relational_impedance_mismatch). The object-relational impedance mismatch also is a major reason why many developers don't like working with traditional ORMs. -As an example, consider how data is organized and relationships are handled with each apprach: +As an example, consider how data is organized and relationships are handled with each approach: - **Relational databases**: Data is typically normalized (flat) and uses foreign keys to link across entities. The entities then need to be JOINed to manifest the actual relationships. - **Object-oriented**: Objects can be deeply nested structures where you can traverse relationships simply by using dot notation.