﻿id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
23597	docs: specifying SingleObjectMixin.model uses default manager, not necessarily objects	Ismail Badawi	Ismail Badawi	"This is a tiny thing I came across. The docs for [https://docs.djangoproject.com/en/1.7/ref/class-based-views/mixins-single-object/#django.views.generic.detail.SingleObjectMixin.model SingleObjectMixin.model] and [https://docs.djangoproject.com/en/1.7/ref/class-based-views/mixins-multiple-object/#django.views.generic.list.MultipleObjectMixin.model MultipleObjectMixin.model] both say:

> The model that this view will display data for. Specifying `model = Foo` is effectively the same as specifying `queryset = Foo.objects.all()`.

But peeking at the code, this isn't quite true -- in both cases ([https://github.com/django/django/blob/8c581ff39475c1b3b25d60945cc1c73a7f8eb1be/django/views/generic/detail.py#L67-L68 here] and [https://github.com/django/django/blob/8c581ff39475c1b3b25d60945cc1c73a7f8eb1be/django/views/generic/list.py#L37-L38 here]), the default manager is used, which is not necessarily `objects`.

Is it worth making this more precise? The docs don't mention default managers very often."	Bug	closed	Documentation	1.7	Normal	fixed			Accepted	1	0	0	0	1	0
