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
3416	Model API documentation section 'Modifying initial Manager QuerySets' misleads about Admin behaviour	Alex Dedul	nobody	"It says:

{{{
If you use custom Manager objects, take note that the first Manager Django encounters 
(in order by which they're defined in the model) has a special status. Django interprets 
the first Manager defined in a class as the ""default"" Manager. Certain operations -- such
as Django's admin site -- use the default Manager to obtain lists of objects, so it's 
generally a good idea for the first Manager to be relatively unfiltered.
}}}

But if you have your custom manager in a model even called 'objects' admin anyway will display all records from model regardless specified custom manager. The only way i found to tell admin to use custom manager is to use 'manager' attribute in inner Admin class in a model. So i guess reference to admin should be removed from here for now and 'manager' attribute of inner Admin class documented instead."		closed	contrib.admin	dev		fixed			Accepted	0	0	0	0	0	0