Skip to content

Commit 2d7595e

Browse files
committed
tweaking wording on orms page
1 parent beed91a commit 2d7595e

4 files changed

Lines changed: 10 additions & 10 deletions

File tree

all.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3371,9 +3371,9 @@ <h3>Potential for reduced performance</h3>
33713371
<h3>Shifting complexity from the database into the app code</h3>
33723372
<p>The code for working with an application's data has to live somewhere. Before
33733373
ORMs were common, database stored procedures were used to encapsulate the
3374-
database logic. With an ORM, the data manipulation code instead lives in the
3375-
application's codebase. The addition of data handling code in the codebase
3376-
generally isn't an issue with a sound application design, but it does
3374+
database logic. With an ORM, the data manipulation code instead lives within
3375+
the application's Python codebase. The addition of data handling logic in the
3376+
codebase generally isn't an issue with a sound application design, but it does
33773377
increase the total amount of Python code instead of splitting code between
33783378
the application and the database stored procedures.</p>
33793379
<h2>Python ORM Implementations</h2>

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:21:39Z</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:22:16Z</updated></feed>

object-relational-mappers-orms.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -131,9 +131,9 @@ <h3>Potential for reduced performance</h3>
131131
<h3>Shifting complexity from the database into the app code</h3>
132132
<p>The code for working with an application's data has to live somewhere. Before
133133
ORMs were common, database stored procedures were used to encapsulate the
134-
database logic. With an ORM, the data manipulation code instead lives in the
135-
application's codebase. The addition of data handling code in the codebase
136-
generally isn't an issue with a sound application design, but it does
134+
database logic. With an ORM, the data manipulation code instead lives within
135+
the application's Python codebase. The addition of data handling logic in the
136+
codebase generally isn't an issue with a sound application design, but it does
137137
increase the total amount of Python code instead of splitting code between
138138
the application and the database stored procedures.</p>
139139
<h2>Python ORM Implementations</h2>

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -121,9 +121,9 @@ SQL code.
121121
### Shifting complexity from the database into the app code
122122
The code for working with an application's data has to live somewhere. Before
123123
ORMs were common, database stored procedures were used to encapsulate the
124-
database logic. With an ORM, the data manipulation code instead lives in the
125-
application's codebase. The addition of data handling code in the codebase
126-
generally isn't an issue with a sound application design, but it does
124+
database logic. With an ORM, the data manipulation code instead lives within
125+
the application's Python codebase. The addition of data handling logic in the
126+
codebase generally isn't an issue with a sound application design, but it does
127127
increase the total amount of Python code instead of splitting code between
128128
the application and the database stored procedures.
129129

0 commit comments

Comments
 (0)