On 04/16/2011 04:30 PM, Carl Meyer wrote:
in general, related-object access for reverse-FKs and M2Ms, contrary to the documentation, will _always_ use your default manager (actually, a dynamic subclass of it)
It kind of makes sense. You don't want your deleted items to appear in results just because you conveniently get a queryset from a related manager. In other words, `topic.article_set.all()` should always yield the same data as `Article.objects.filter(topic=topic)`.
But I would agree that in this case:
even if "use_for_related_fields" is absent or explicitly set to False on your Manager subclass.
… the default manager should not be used as a base class. Fixing just this would be the best option because it retains current behavior by default while allowing other uses if needed.
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
