<feed xmlns='http://www.w3.org/2005/Atom'>
<title>django.git/django/db/models/sql/query.py, branch 1.3</title>
<subtitle>django
</subtitle>
<id>http://cgit.adnoto.dev/django.git/atom?h=1.3</id>
<link rel='self' href='http://cgit.adnoto.dev/django.git/atom?h=1.3'/>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/'/>
<updated>2011-03-14T19:49:53Z</updated>
<entry>
<title>Fixed #14733: no longer "validate" .raw() queries.</title>
<updated>2011-03-14T19:49:53Z</updated>
<author>
<name>Jacob Kaplan-Moss</name>
<email>jacob@jacobian.org</email>
</author>
<published>2011-03-14T19:49:53Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=fd2f18008caeca28c60c43cce7b43fb87c6fee78'/>
<id>urn:sha1:fd2f18008caeca28c60c43cce7b43fb87c6fee78</id>
<content type='text'>
Turns out that a lot more than just SELECT can return data, and this list is
very hard to define up front in a cross-database manner. So let's just assume
that anyone using raw() is at least halfway competant and can deal with
the error messages if they don't use a data-returning query.

Thanks to Christophe Pettus for the patch.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15803 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
<entry>
<title>Fixed #12252 -- Ensure that queryset unions are commutative. Thanks to benreynwar for the report, and draft patch, and to Karen and Ramiro for the review eyeballs and patch updates.</title>
<updated>2011-03-03T13:51:54Z</updated>
<author>
<name>Russell Keith-Magee</name>
<email>russell@keith-magee.com</email>
</author>
<published>2011-03-03T13:51:54Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=b7c41c1fbb2d45634dde5f7a450ba1a5aea5a8af'/>
<id>urn:sha1:b7c41c1fbb2d45634dde5f7a450ba1a5aea5a8af</id>
<content type='text'>
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15726 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
<entry>
<title>Fixed #13815 -- Ensure that reverse exclude lookups on nullable foreign keys exclude null values. Thanks to bpeschier for the report and patch.</title>
<updated>2011-02-08T14:06:02Z</updated>
<author>
<name>Russell Keith-Magee</name>
<email>russell@keith-magee.com</email>
</author>
<published>2011-02-08T14:06:02Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=d3b38d578f41240442cb043012b0035a20eebd67'/>
<id>urn:sha1:d3b38d578f41240442cb043012b0035a20eebd67</id>
<content type='text'>
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15458 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
<entry>
<title>Fixed #15161 - Corrected handling of ManyToManyField with through table using to_field on its ForeignKeys. Thanks to adehnert for the report.</title>
<updated>2011-01-26T19:10:08Z</updated>
<author>
<name>Carl Meyer</name>
<email>carl@oddbird.net</email>
</author>
<published>2011-01-26T19:10:08Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=84291b7b8456b554f162b6eeaffa9b124907c1d2'/>
<id>urn:sha1:84291b7b8456b554f162b6eeaffa9b124907c1d2</id>
<content type='text'>
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15330 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
<entry>
<title>Tweaked r15303 to avoid O(N) lookup of field name. Thanks to Alex's eagle eyes.</title>
<updated>2011-01-26T08:39:30Z</updated>
<author>
<name>Carl Meyer</name>
<email>carl@oddbird.net</email>
</author>
<published>2011-01-26T08:39:30Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=a9b4f2a40043cdf8e61dce7e623028ba33ffd6af'/>
<id>urn:sha1:a9b4f2a40043cdf8e61dce7e623028ba33ffd6af</id>
<content type='text'>
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15324 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
<entry>
<title>Fixed #11319 - Added lookup support for ForeignKey.to_field. Also reverted no-longer-needed model formsets workaround for lack of such support from r10756. Thanks Russell and Alex for review.</title>
<updated>2011-01-25T03:14:28Z</updated>
<author>
<name>Carl Meyer</name>
<email>carl@oddbird.net</email>
</author>
<published>2011-01-25T03:14:28Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=227c5e80dbff2b731a1cba8c4dd94c00526a3e76'/>
<id>urn:sha1:227c5e80dbff2b731a1cba8c4dd94c00526a3e76</id>
<content type='text'>
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15303 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
<entry>
<title>Cleaned up the ORM slightly.</title>
<updated>2011-01-14T05:04:14Z</updated>
<author>
<name>Alex Gaynor</name>
<email>alex.gaynor@gmail.com</email>
</author>
<published>2011-01-14T05:04:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=92d43522839fd9ec945d8c018de78770bec04ee1'/>
<id>urn:sha1:92d43522839fd9ec945d8c018de78770bec04ee1</id>
<content type='text'>
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15203 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
<entry>
<title>Fixed #11293 -- fixed using Q objects to generate ORs with aggregates.</title>
<updated>2011-01-11T01:00:50Z</updated>
<author>
<name>Alex Gaynor</name>
<email>alex.gaynor@gmail.com</email>
</author>
<published>2011-01-11T01:00:50Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=29de7ee9cb78f4216faec7499044fdf65c1b2511'/>
<id>urn:sha1:29de7ee9cb78f4216faec7499044fdf65c1b2511</id>
<content type='text'>
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15173 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
<entry>
<title>Fixed a suite of errors in the ORM -- a) fixed calling values_list().values_list() and changing whether the results are flat, b) fixed an issue with fields on the left-hand side of what becomes the HAVING clause not being included in the GROUP BY clause, and c) fixed a bug with fields from values() calls not being included in the GROUP BY clause.  This fixed the recent test failures under postgresql.</title>
<updated>2010-11-26T14:24:08Z</updated>
<author>
<name>Alex Gaynor</name>
<email>alex.gaynor@gmail.com</email>
</author>
<published>2010-11-26T14:24:08Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=678f626c24f389b03d4bfe2c552c33e9bdcc9379'/>
<id>urn:sha1:678f626c24f389b03d4bfe2c552c33e9bdcc9379</id>
<content type='text'>
git-svn-id: http://code.djangoproject.com/svn/django/trunk@14715 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
<entry>
<title>Fixed #14423 -- corrected incorrect SQL being generated when a nullable, inherited field was used in an exclude.  Thanks to PhiR_42 for the patch.</title>
<updated>2010-11-17T16:46:50Z</updated>
<author>
<name>Alex Gaynor</name>
<email>alex.gaynor@gmail.com</email>
</author>
<published>2010-11-17T16:46:50Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=0eb31d3dc9435b18680f7a41bc9067685beb8344'/>
<id>urn:sha1:0eb31d3dc9435b18680f7a41bc9067685beb8344</id>
<content type='text'>
git-svn-id: http://code.djangoproject.com/svn/django/trunk@14600 bcc190cf-cafb-0310-a4f2-bffc1f526a37
</content>
</entry>
</feed>
