| commit | 8dc9446c1fac846eb4f42c967b4f299e37c37b95 | |
| author | mtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37> | |
| Wed, 27 Aug 2008 05:22:33 +0000 (27 05:22 +0000) | ||
| committer | mtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37> | |
| Wed, 27 Aug 2008 05:22:33 +0000 (27 05:22 +0000) | ||
| tree | 4e535929ca860db1c5a030775c29475506af3505 | treesnapshot (tar.gz zip) |
| parent | f090e34e97f96c9df6efe21b897789d9d11fdab6 | commitdiff |
Fixed #5937 -- When filtering on generic relations, restrict the target objects to those with the right content type.
This isn't a complete solution to this class of problem, but it will do for
1.0, which only has generic relations as a multicolumn type. A more general
multicolumn solution will be available after that release.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8608 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This isn't a complete solution to this class of problem, but it will do for
1.0, which only has generic relations as a multicolumn type. A more general
multicolumn solution will be available after that release.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8608 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| django/contrib/contenttypes/generic.py | diffblobblamehistory | |
| django/db/models/sql/query.py | diffblobblamehistory | |
| tests/modeltests/generic_relations/models.py | diffblobblamehistory |