<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for Jan</title><link>http://disqus.com/people/39d14af7be34ffda95d7075304c8cba1/</link><description></description><language>en</language><lastBuildDate>Tue, 22 Jan 2008 00:47:42 -0000</lastBuildDate><item><title>Re: Caching Layer for Django ORM</title><link>http://davidcramer.disqus.com/caching_layer_for_django_orm/#comment-3320397</link><description>I like this a lot! When I started developing my django app most pages made like 50 seperate foreign key requests each for a single ID to the database. I even had queries for the same ID.&lt;br&gt;&lt;br&gt;Because I really have to focus on DB speed I can't use Django's select_related function. That's why I'm now caching foreign key lookups with memcache get_many calls (Just hacked this code direclty editing Django sources for now).&lt;br&gt;&lt;br&gt;I had most problems with foreign key lookups and obviously count() queries - and it's amazing to have Django's ORM to manage all that caching transparently behind the scenes. Great job!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jan</dc:creator><pubDate>Tue, 22 Jan 2008 00:47:42 -0000</pubDate></item></channel></rss>