new orm resource

mattmakai · mattmakai · commit a7d69f87f685 · 2017-02-01T07:56:40.000-08:00
diff --git a/all.html b/all.html
@@ -8580,7 +8580,7 @@ <h3>Django's ORM</h3>
 for simple and medium-complexity database operations. However, there are often
 complaints that the ORM makes complex queries much more complicated than
 writing straight SQL or using <a href="http://www.sqlalchemy.org/">SQLAlchemy</a>.</p>
-<p>It's technically possible to drop down to SQL but it ties the queries to a
+<p>It is technically possible to drop down to SQL but it ties the queries to a
 specific database implementation. The ORM is coupled closely with Django so
 replacing the default ORM with SQLAlchemy is currently a hack workaround. Note
 though that some of the Django core committers believe it is only a matter of
@@ -8673,6 +8673,13 @@ <h3>General ORM resources</h3>
   and another one from Ted entitled 
   <a href="http://blogs.tedneward.com/post/thoughts-on-vietnam-commentary/">thoughts on Vietnam commentary</a>.</p>
 </li>
+<li>
+<p><a href="https://medium.com/@bradurani/turning-the-tables-how-to-get-along-with-your-object-relational-mapper-e5d2d6a76573">Turning the Tables: How to Get Along with your Object-Relational Mapper</a>
+  coins the funny but insightful phrase "database denial" to describe how
+  some ORMs provide a usage model that can cause more issues than they
+  solve over straight SQL queries. The post then goes into much more detail
+  about the problems that can arise and how to mitigate or avoid them.</p>
+</li>
 </ul>
 <h3>SQLAlchemy and Peewee resources</h3>
 <p>A comprehensive list of <a href="/sqlalchemy.html">SQLAlchemy</a> and 
diff --git a/object-relational-mappers-orms.html b/object-relational-mappers-orms.html
@@ -158,7 +158,7 @@ <h3>Django's ORM</h3>
 for simple and medium-complexity database operations. However, there are often
 complaints that the ORM makes complex queries much more complicated than
 writing straight SQL or using <a href="http://www.sqlalchemy.org/">SQLAlchemy</a>.</p>
-<p>It's technically possible to drop down to SQL but it ties the queries to a
+<p>It is technically possible to drop down to SQL but it ties the queries to a
 specific database implementation. The ORM is coupled closely with Django so
 replacing the default ORM with SQLAlchemy is currently a hack workaround. Note
 though that some of the Django core committers believe it is only a matter of
@@ -251,6 +251,13 @@ <h3>General ORM resources</h3>
   and another one from Ted entitled 
   <a href="http://blogs.tedneward.com/post/thoughts-on-vietnam-commentary/">thoughts on Vietnam commentary</a>.</p>
 </li>
+<li>
+<p><a href="https://medium.com/@bradurani/turning-the-tables-how-to-get-along-with-your-object-relational-mapper-e5d2d6a76573">Turning the Tables: How to Get Along with your Object-Relational Mapper</a>
+  coins the funny but insightful phrase "database denial" to describe how
+  some ORMs provide a usage model that can cause more issues than they
+  solve over straight SQL queries. The post then goes into much more detail
+  about the problems that can arise and how to mitigate or avoid them.</p>
+</li>
 </ul>
 <h3>SQLAlchemy and Peewee resources</h3>
 <p>A comprehensive list of <a href="/sqlalchemy.html">SQLAlchemy</a> and 
diff --git a/source/content/pages/09-data/06-object-relational-mappers.markdown b/source/content/pages/09-data/06-object-relational-mappers.markdown
@@ -155,7 +155,7 @@ for simple and medium-complexity database operations. However, there are often
 complaints that the ORM makes complex queries much more complicated than
 writing straight SQL or using [SQLAlchemy](http://www.sqlalchemy.org/).
 
-It's technically possible to drop down to SQL but it ties the queries to a
+It is technically possible to drop down to SQL but it ties the queries to a
 specific database implementation. The ORM is coupled closely with Django so
 replacing the default ORM with SQLAlchemy is currently a hack workaround. Note
 though that some of the Django core committers believe it is only a matter of
@@ -256,6 +256,12 @@ For now, we'll lump schema migration resources under ORM links below.
   and another one from Ted entitled 
   [thoughts on Vietnam commentary](http://blogs.tedneward.com/post/thoughts-on-vietnam-commentary/).
 
+* [Turning the Tables: How to Get Along with your Object-Relational Mapper](https://medium.com/@bradurani/turning-the-tables-how-to-get-along-with-your-object-relational-mapper-e5d2d6a76573)
+  coins the funny but insightful phrase "database denial" to describe how
+  some ORMs provide a usage model that can cause more issues than they
+  solve over straight SQL queries. The post then goes into much more detail
+  about the problems that can arise and how to mitigate or avoid them.
+
 
 ### SQLAlchemy and Peewee resources
 A comprehensive list of [SQLAlchemy](/sqlalchemy.html) and 
