django.git/tests/regressiontests/custom_managers_regress/models.py, branch archive/soc2010/test-refactordjango
http://cgit.adnoto.dev/django.git/atom?h=archive%2Fsoc2010%2Ftest-refactor2010-08-24T01:03:51Z[soc2010/test-refactor] converted custom_managers_regress2010-08-24T01:03:51ZPaul McMillanPaul@McMillan.ws2010-08-24T01:03:51Zurn:sha1:fe09017f70f2687f972b8a4358247fd4be8090c1
git-svn-id: http://code.djangoproject.com/svn/django/branches/soc2010/test-refactor@13635 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Fixed #2698 -- Fixed deleting in the presence of custom managers.2009-03-20T03:57:12ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2009-03-20T03:57:12Zurn:sha1:fa89fdcd6b4a4ab4887740c0d0f4a73297a5b060
A custom manager on a related object that filtered away objects would prevent
those objects being deleted via the relation. This is now fixed.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@10104 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Use plain model.Manager, or suitable proxy, for model saving.2009-03-15T03:41:33ZMalcolm Tredinnickmalcolm.tredinnick@gmail.com2009-03-15T03:41:33Zurn:sha1:7d9b29a56ddc1a793a02d55743c372a8256b97aa
We can't use the default manager in Model.save_base(), since we need to
retrieve existing objects which might be filtered out by that manager. We now
always use a plain Manager instance at that point (or something that can
replace it, such as a GeoManager), making all existing rows in the
database visible to the saving code.
The logic for detecting a "suitable replacement" plain base is the same as for
related fields: if the use_for_related_fields is set on the manager subclass,
we can use it. The general requirement here is that we want a base class that
returns the appropriate QuerySet subclass, but does not restrict the rows
returned.
Fixed #8990, #9527.
Refs #2698 (which is not fixed by this change, but it's the first part of a
larger change to fix that bug.)
git-svn-id: http://code.djangoproject.com/svn/django/trunk@10056 bcc190cf-cafb-0310-a4f2-bffc1f526a37