<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Model Downcast in Django</title>
	<atom:link href="http://blog.mauveweb.co.uk/2008/07/30/model-downcast-in-django/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mauveweb.co.uk/2008/07/30/model-downcast-in-django/</link>
	<description>experiments in contemporary web development</description>
	<pubDate>Wed, 07 Jan 2009 10:12:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Ryan</title>
		<link>http://blog.mauveweb.co.uk/2008/07/30/model-downcast-in-django/#comment-24430</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Thu, 31 Jul 2008 00:48:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mauveweb.co.uk/?p=154#comment-24430</guid>
		<description>I just ran across this problem today.  I wanted to query the parent model and use each instance returned as a child model, but instead I just queried each of the child tables one at a time.  I think SQLAlchemy handles this better.</description>
		<content:encoded><![CDATA[<p>I just ran across this problem today.  I wanted to query the parent model and use each instance returned as a child model, but instead I just queried each of the child tables one at a time.  I think SQLAlchemy handles this better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
