Skip to content

Commit 846c6c8

Browse files
mattmakaimattmakai
committed
tweaking orms page wording
1 parent a76bbe0 commit 846c6c8

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

‎all.html‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3402,8 +3402,8 @@ <h3>Django's ORM</h3>
34023402
replacing the default ORM with SQLAlchemy is currently a hack workaround. Note
34033403
though that some of the Django core committers believe it is only a matter of
34043404
time before the default ORM is replaced with SQLAlchemy. It will be a large
3405-
effort to get that working though so it's likely to come in Django 1.9 or
3406-
later.</p>
3405+
effort to get that working though so it's likely to come in
3406+
<a href="https://github.com/makaimc/fullstackpython.com/issues/48">Django 1.9 or later</a>.</p>
34073407
<p>Since the majority of Django projects are tied to the default ORM, it's best to
34083408
read up on advanced use cases and tools for doing your best work within the
34093409
existing framework.</p>

‎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:23:03Z</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:24:33Z</updated></feed>

‎object-relational-mappers-orms.html‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -162,8 +162,8 @@ <h3>Django's ORM</h3>
162162
replacing the default ORM with SQLAlchemy is currently a hack workaround. Note
163163
though that some of the Django core committers believe it is only a matter of
164164
time before the default ORM is replaced with SQLAlchemy. It will be a large
165-
effort to get that working though so it's likely to come in Django 1.9 or
166-
later.</p>
165+
effort to get that working though so it's likely to come in
166+
<a href="https://github.com/makaimc/fullstackpython.com/issues/48">Django 1.9 or later</a>.</p>
167167
<p>Since the majority of Django projects are tied to the default ORM, it's best to
168168
read up on advanced use cases and tools for doing your best work within the
169169
existing framework.</p>

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -158,8 +158,8 @@ specific database implementation. The ORM is coupled closely with Django so
158158
replacing the default ORM with SQLAlchemy is currently a hack workaround. Note
159159
though that some of the Django core committers believe it is only a matter of
160160
time before the default ORM is replaced with SQLAlchemy. It will be a large
161-
effort to get that working though so it's likely to come in Django 1.9 or
162-
later.
161+
effort to get that working though so it's likely to come in
162+
[Django 1.9 or later](https://github.com/makaimc/fullstackpython.com/issues/48).
163163

164164
Since the majority of Django projects are tied to the default ORM, it's best to
165165
read up on advanced use cases and tools for doing your best work within the

0 commit comments

Comments
 (0)