Skip to content

Commit a1ab537

Browse files
mattmakaimattmakai
committed
tweaking wording on orms page
1 parent 7235084 commit a1ab537

4 files changed

Lines changed: 37 additions & 40 deletions

File tree

‎all.html‎

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -3347,10 +3347,9 @@ <h3>Impedance mismatch</h3>
33473347
moving data between relational tables and application objects. The gist
33483348
is that the way a developer uses objects is different from how data is
33493349
stored and joined in relational tables.</p>
3350-
<p>This article does a solid job of explaing what
3351-
<a href="http://www.agiledata.org/essays/impedanceMismatch.html">ORM impedance mismatch</a>
3352-
is at a high level and provides diagrams to visualize why the problem
3353-
occurs. </p>
3350+
<p><a href="http://www.agiledata.org/essays/impedanceMismatch.html">This article on ORM impedance mismatch</a>
3351+
does a solid job of explaing what the concept is at a high level and
3352+
provides diagrams to visualize why the problem occurs. </p>
33543353
<h3>Potential for reduced performance</h3>
33553354
<p>One of the concerns that's associated with any higher-level abstraction or
33563355
framework is potential for reduced performance. With ORMs, the performance
@@ -3359,16 +3358,16 @@ <h3>Potential for reduced performance</h3>
33593358
<p>ORMs are also often easy to try but difficult to master. For example, a
33603359
beginner using Django might not know about the
33613360
<a href="https://docs.djangoproject.com/en/1.8/ref/models/querysets/#select-related"><code>select_related()</code> function</a>
3362-
or how that can dramatically improve some queries' performance with
3363-
foreign key relationships. There are dozens of performance tips and tricks
3364-
for every ORM and it's possible that investing time in learning those
3365-
quirks may be better spent just learning SQL and how to write stored
3366-
procedures.</p>
3361+
and how it can improve some queries' foreign key relationship performance.
3362+
There are dozens of performance tips and tricks for every ORM. It's possible
3363+
that investing time in learning those quirks may be better spent just
3364+
learning SQL and how to write stored procedures.</p>
33673365
<p>There's a lot of hand-waving "may or may not" and "potential for" in this
3368-
section. In most cases ORMs are good enough for roughly 80-90% of use cases
3369-
and in 10-20% of database interactions there can be major performance
3370-
improvements by having a knowledgeable database adminstrator write tuned
3371-
SQL statements to replace the ORM's generated SQL code.</p>
3366+
section. In large projects ORMs are good enough for roughly 80-90% of use
3367+
cases but in 10-20% of a project's database interactions there can be
3368+
major performance improvements by having a knowledgeable database
3369+
adminstrator write tuned SQL statements to replace the ORM's generated
3370+
SQL code.</p>
33723371
<h3>Shifting complexity from the DB into the app code</h3>
33733372
<p>The code for working with an application's data has to live somewhere. Before
33743373
ORMs were common, database stored procedures were used to encapsulate the

‎feeds/all.atom.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
<?xml version="1.0" encoding="utf-8"?>
2-
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-06-16T09:16:59Z</updated></feed>
2+
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-06-16T09:21:17Z</updated></feed>

‎object-relational-mappers-orms.html‎

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -107,10 +107,9 @@ <h3>Impedance mismatch</h3>
107107
moving data between relational tables and application objects. The gist
108108
is that the way a developer uses objects is different from how data is
109109
stored and joined in relational tables.</p>
110-
<p>This article does a solid job of explaing what
111-
<a href="http://www.agiledata.org/essays/impedanceMismatch.html">ORM impedance mismatch</a>
112-
is at a high level and provides diagrams to visualize why the problem
113-
occurs. </p>
110+
<p><a href="http://www.agiledata.org/essays/impedanceMismatch.html">This article on ORM impedance mismatch</a>
111+
does a solid job of explaing what the concept is at a high level and
112+
provides diagrams to visualize why the problem occurs. </p>
114113
<h3>Potential for reduced performance</h3>
115114
<p>One of the concerns that's associated with any higher-level abstraction or
116115
framework is potential for reduced performance. With ORMs, the performance
@@ -119,16 +118,16 @@ <h3>Potential for reduced performance</h3>
119118
<p>ORMs are also often easy to try but difficult to master. For example, a
120119
beginner using Django might not know about the
121120
<a href="https://docs.djangoproject.com/en/1.8/ref/models/querysets/#select-related"><code>select_related()</code> function</a>
122-
or how that can dramatically improve some queries' performance with
123-
foreign key relationships. There are dozens of performance tips and tricks
124-
for every ORM and it's possible that investing time in learning those
125-
quirks may be better spent just learning SQL and how to write stored
126-
procedures.</p>
121+
and how it can improve some queries' foreign key relationship performance.
122+
There are dozens of performance tips and tricks for every ORM. It's possible
123+
that investing time in learning those quirks may be better spent just
124+
learning SQL and how to write stored procedures.</p>
127125
<p>There's a lot of hand-waving "may or may not" and "potential for" in this
128-
section. In most cases ORMs are good enough for roughly 80-90% of use cases
129-
and in 10-20% of database interactions there can be major performance
130-
improvements by having a knowledgeable database adminstrator write tuned
131-
SQL statements to replace the ORM's generated SQL code.</p>
126+
section. In large projects ORMs are good enough for roughly 80-90% of use
127+
cases but in 10-20% of a project's database interactions there can be
128+
major performance improvements by having a knowledgeable database
129+
adminstrator write tuned SQL statements to replace the ORM's generated
130+
SQL code.</p>
132131
<h3>Shifting complexity from the DB into the app code</h3>
133132
<p>The code for working with an application's data has to live somewhere. Before
134133
ORMs were common, database stored procedures were used to encapsulate the

‎source/content/pages/05-data/04-object-relational-mappers.markdown‎

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -91,10 +91,9 @@ moving data between relational tables and application objects. The gist
9191
is that the way a developer uses objects is different from how data is
9292
stored and joined in relational tables.
9393

94-
This article does a solid job of explaing what
95-
[ORM impedance mismatch](http://www.agiledata.org/essays/impedanceMismatch.html)
96-
is at a high level and provides diagrams to visualize why the problem
97-
occurs.
94+
[This article on ORM impedance mismatch](http://www.agiledata.org/essays/impedanceMismatch.html)
95+
does a solid job of explaing what the concept is at a high level and
96+
provides diagrams to visualize why the problem occurs.
9897

9998

10099
### Potential for reduced performance
@@ -106,17 +105,17 @@ statement which may not be tuned properly.
106105
ORMs are also often easy to try but difficult to master. For example, a
107106
beginner using Django might not know about the
108107
[`select_related()` function](https://docs.djangoproject.com/en/1.8/ref/models/querysets/#select-related)
109-
or how that can dramatically improve some queries' performance with
110-
foreign key relationships. There are dozens of performance tips and tricks
111-
for every ORM and it's possible that investing time in learning those
112-
quirks may be better spent just learning SQL and how to write stored
113-
procedures.
108+
and how it can improve some queries' foreign key relationship performance.
109+
There are dozens of performance tips and tricks for every ORM. It's possible
110+
that investing time in learning those quirks may be better spent just
111+
learning SQL and how to write stored procedures.
114112

115113
There's a lot of hand-waving "may or may not" and "potential for" in this
116-
section. In most cases ORMs are good enough for roughly 80-90% of use cases
117-
and in 10-20% of database interactions there can be major performance
118-
improvements by having a knowledgeable database adminstrator write tuned
119-
SQL statements to replace the ORM's generated SQL code.
114+
section. In large projects ORMs are good enough for roughly 80-90% of use
115+
cases but in 10-20% of a project's database interactions there can be
116+
major performance improvements by having a knowledgeable database
117+
adminstrator write tuned SQL statements to replace the ORM's generated
118+
SQL code.
120119

121120

122121
### Shifting complexity from the DB into the app code

0 commit comments

Comments
 (0)