<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Diving into Django</title>
	<atom:link href="http://www.protocolostomy.com/2008/02/27/diving-into-django/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.protocolostomy.com/2008/02/27/diving-into-django/</link>
	<description>Made with only the finest 1's and 0's</description>
	<lastBuildDate>Thu, 26 Jan 2012 21:20:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Doug Hellmann</title>
		<link>http://www.protocolostomy.com/2008/02/27/diving-into-django/comment-page-1/#comment-183</link>
		<dc:creator>Doug Hellmann</dc:creator>
		<pubDate>Thu, 28 Feb 2008 02:34:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/2008/02/27/diving-into-django/#comment-183</guid>
		<description>Moving from sqlite to postgresql is *mostly* trivial, but I seem to have a particular knack for finding edge cases where the move doesn&#039;t work.  Since each db has a different backend implementation under the ORM, sometimes queries aren&#039;t translated in quite the same way.  There&#039;s always http://www.postgresqlformac.com/ though, so you can use that for dev if you do run into any issues.</description>
		<content:encoded><![CDATA[<p>Moving from sqlite to postgresql is *mostly* trivial, but I seem to have a particular knack for finding edge cases where the move doesn&#8217;t work.  Since each db has a different backend implementation under the ORM, sometimes queries aren&#8217;t translated in quite the same way.  There&#8217;s always <a href="http://www.postgresqlformac.com/" rel="nofollow">http://www.postgresqlformac.com/</a> though, so you can use that for dev if you do run into any issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.protocolostomy.com/2008/02/27/diving-into-django/comment-page-1/#comment-182</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Thu, 28 Feb 2008 02:00:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/2008/02/27/diving-into-django/#comment-182</guid>
		<description>I&#039;d just add that although Django will serve you all the &quot;kool-aid&quot; you can drink its easy to swap out the components that don&#039;t suit your style. For instance, I love Django (it really goes make web development &quot;stupidly&quot; fast), but I prefer Mako templates over the default as they put the full power of python in your view layer. It easy to miss this when the framework is presented as such an integrated package.</description>
		<content:encoded><![CDATA[<p>I&#8217;d just add that although Django will serve you all the &#8220;kool-aid&#8221; you can drink its easy to swap out the components that don&#8217;t suit your style. For instance, I love Django (it really goes make web development &#8220;stupidly&#8221; fast), but I prefer Mako templates over the default as they put the full power of python in your view layer. It easy to miss this when the framework is presented as such an integrated package.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

