<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Django Aware &#187; Database API Revisions</title>
	<atom:link href="http://blog.awarelabs.com/category/django_revisions/database_api_revisions/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.awarelabs.com</link>
	<description>Django is for the Aware</description>
	<lastBuildDate>Tue, 06 Apr 2010 16:52:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>OneToOne Fields And The Primary Key Issue</title>
		<link>http://blog.awarelabs.com/2008/onetoone-fields-and-the-primary-key-issue/</link>
		<comments>http://blog.awarelabs.com/2008/onetoone-fields-and-the-primary-key-issue/#comments</comments>
		<pubDate>Mon, 23 Jun 2008 16:27:04 +0000</pubDate>
		<dc:creator>Paul Kenjora</dc:creator>
				<category><![CDATA[Database API Revisions]]></category>
		<category><![CDATA[Model Revisions]]></category>
		<category><![CDATA[Tutorial]]></category>

		<guid isPermaLink="false">http://blog.awarelabs.com/?p=64</guid>
		<description><![CDATA[Django provides one-many ForeignKey, many-many ManyToManyField, and one-one OneToOneField options for defining table relationships.  The OneToOneField specifically has recently been the topic of heated debates and ideas.  Unlike the other options this field is by always constrained to be a &#8220;Primary Key&#8221;.  The restriction implies that each table may ONLY have one [...]]]></description>
		<wfw:commentRss>http://blog.awarelabs.com/2008/onetoone-fields-and-the-primary-key-issue/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Django Deserializer Bug On Foreign Key When None</title>
		<link>http://blog.awarelabs.com/2008/django-deserializer-bug-on-foreign-key-when-none/</link>
		<comments>http://blog.awarelabs.com/2008/django-deserializer-bug-on-foreign-key-when-none/#comments</comments>
		<pubDate>Tue, 19 Feb 2008 03:10:43 +0000</pubDate>
		<dc:creator>Paul Kenjora</dc:creator>
				<category><![CDATA[Database API Revisions]]></category>
		<category><![CDATA[Tutorial]]></category>

		<guid isPermaLink="false">http://blog.awarelabs.com/?p=38</guid>
		<description><![CDATA[THis is more for myself than anyone else but remind me to submit this to the bug list.  Or at least check if it exists already.  When deserializing a model with a foreign key whose value is set to None I get the following exeption:
The Bug

  File "/home2/pkenjora/lib/python2.4/django/core/serializers/python.py", line 82, in Deserializer
 [...]]]></description>
		<wfw:commentRss>http://blog.awarelabs.com/2008/django-deserializer-bug-on-foreign-key-when-none/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Modify Django To Support Group By Query Function</title>
		<link>http://blog.awarelabs.com/2007/modify-django-to-support-group-by-query-function/</link>
		<comments>http://blog.awarelabs.com/2007/modify-django-to-support-group-by-query-function/#comments</comments>
		<pubDate>Mon, 10 Sep 2007 03:02:30 +0000</pubDate>
		<dc:creator>Paul Kenjora</dc:creator>
				<category><![CDATA[Code Snippets]]></category>
		<category><![CDATA[Database API Revisions]]></category>
		<category><![CDATA[Django Revisions]]></category>

		<guid isPermaLink="false">http://blog.awarelabs.com/?p=19</guid>
		<description><![CDATA[Group by is used extensively in many day to day SQL queries.  Although most often it is used for counting sometimes group by comes in handy for creating an artificial unique constraint.  For example say you have a list of URLS that are described by a checksum and you wish to query a [...]]]></description>
		<wfw:commentRss>http://blog.awarelabs.com/2007/modify-django-to-support-group-by-query-function/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Modify Django To Support Binary Order By</title>
		<link>http://blog.awarelabs.com/2007/modify-django-to-support-binary-search/</link>
		<comments>http://blog.awarelabs.com/2007/modify-django-to-support-binary-search/#comments</comments>
		<pubDate>Mon, 20 Aug 2007 06:25:54 +0000</pubDate>
		<dc:creator>Paul Kenjora</dc:creator>
				<category><![CDATA[Code Snippets]]></category>
		<category><![CDATA[Database API Revisions]]></category>
		<category><![CDATA[Django Revisions]]></category>

		<guid isPermaLink="false">http://blog.awarelabs.com/?p=18</guid>
		<description><![CDATA[Binary order by is different from simple order by in that it is case sensitive.  Python&#8217;s string comparison operators are also case sensitive.  So for any order_by query on a string column in MySQL the results are not in the order Python expects.  This leads to serious problems when you try to [...]]]></description>
		<wfw:commentRss>http://blog.awarelabs.com/2007/modify-django-to-support-binary-search/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
