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
16048	GenericForeignKey always uses a default manager of a related model	Ivan Virabyan	nobody	"From Django docs:
By default, Django uses an instance of a ""plain"" manager class when accessing related objects (i.e. choice.poll), not the default manager on the related object. This is because Django needs to be able to retrieve the related object, even if it would otherwise be filtered out (and hence be inaccessible) by the default manager.

This is true for ForeignKey, but not GenericForeignKey. So I have no ability to use custom managers for my models, because they are being filtered when I'm accessing related objects."	Bug	closed	contrib.contenttypes	1.3	Normal	fixed	genericforeignkey manager	me@…	Ready for checkin	1	0	0	0	0	0