django.git/django/db/models/sql/query.py, branch 1.0.1django
http://cgit.adnoto.dev/django.git/atom?h=1.0.12008-10-24T09:40:12Z[1.0.X] Fixed #9307 -- Added the ability to pickle the Query class used by the2008-10-24T09:40:12ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-10-24T09:40:12Zurn:sha1:74c799d21d6682eb0a0ed8fa25dc48787d5bfb86
Oracle backend.
This allows Querysets to be cached for Oracle and should provide a model for
adding pickling support to other (external) database backends that need a
custom Query class.
Thanks to Justin Bronn for some assistance with this patch.
Backport of r9272 from trunk.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9273 bcc190cf-cafb-0310-a4f2-bffc1f526a37
[1.0.X] Fixed #9406 -- Ensure that each database column is only represented2008-10-24T06:11:37ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-10-24T06:11:37Zurn:sha1:b52e45193f25e8444d3d5eef4f83d0ee8f7a80b0
once in the "ORDER BY" clause of an SQL statement.
Backport of r9251 from trunk.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9252 bcc190cf-cafb-0310-a4f2-bffc1f526a37
[1.0.X] A queryset that has had ordering removed (order_by()) can have ordering2008-10-08T09:48:21ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-10-08T09:48:21Zurn:sha1:a9936d0b1cc9a0f7468fed87192f60fc5a85c26a
added again later (order_by('foo')). Or, at least, it can now. Thanks to Ilya
Novoselov for diagnosing the problem here.
Backport of r9206 from trunk.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9207 bcc190cf-cafb-0310-a4f2-bffc1f526a37
[1.0.X] Applying a limit to a queryset that already had an upper limit of 02008-10-08T08:43:31ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-10-08T08:43:31Zurn:sha1:09d84c4d40d1d9796f1d0f52bc3ea1bb93a68435
wasn't working properly.
Backport of r9201 from trunk.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9204 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Fixed a missing variable initialisation deep in the Query bowels.2008-09-22T00:31:22ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-09-22T00:31:22Zurn:sha1:922aba3def68e57c405a0e50d353a790af85b00a
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9081 bcc190cf-cafb-0310-a4f2-bffc1f526a37
A bug from queryset-refactor days: although the Query class has "group_by" and2008-09-11T02:00:27ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-09-11T02:00:27Zurn:sha1:e47cc781d844eea72e677d1d212b2dfd1b0c9225
"having" attributes, only the former was included in the resulting SQL, meaning
subclasses had to completely duplicate Query.as_sql() if they were using any
kind of grouping filtering on the results.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9007 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Fixed #8819 -- Don't include two copies of extra-select columns in the query.2008-09-03T03:48:25ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-09-03T03:48:25Zurn:sha1:61cc4a1eeefe734e258c968293529ab070d4d76a
This was triggered by r8794, but was, in fact, fairly fragile before then. The
current fix is the correct way we should be doing this.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8898 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Fixed #8790 -- Multi-branch join trees that shared tables of the same name were2008-09-02T13:52:07ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-09-02T13:52:07Zurn:sha1:5c32fe7fad5c52fb5b62dc97503aed516bb9c668
sometimes also sharing aliases, instead of creating their own. This was
generating incorrect SQL.
No representative test for this fix yet because I haven't had time to write one
that fits in nicely with the test suite. But it works for the monstrous example
in #8790 and a bunch of other complex examples I've created locally. Will write
a test later.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8853 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Fixed #8439 -- Complex combinations of Q-objects (using both conjunctions and2008-09-02T02:16:41ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-09-02T02:16:41Zurn:sha1:12f625990392d49018d0397a7c7bf55286f9b212
disjunctions) were producing incorrect SQL when nullable relations were
involved. This fixes that.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8832 bcc190cf-cafb-0310-a4f2-bffc1f526a37
A typo fix that fortunately wasn't creating invalid SQL, just slightly less2008-09-02T00:50:19ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2008-09-02T00:50:19Zurn:sha1:3cdfb47e9315672cdf06443b32feb62e1f0c0d42
efficient than possible SQL in some odd cases (found via code inspection, not
any particular failing example).
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8831 bcc190cf-cafb-0310-a4f2-bffc1f526a37