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
8119	Accessing single related (parent) objects should not bypass manager	Ivan Sagalaev	nobody	"This is a spun-of from http://code.djangoproject.com/ticket/7666#comment:7 with the relevant discussion here: http://groups.google.com/group/django-developers/browse_frm/thread/a2326c32f8860fb0/

The solution is to have a separate queryset factory on a manager {{{get_full_query_set}}} that can be overridden but is required to return all records. Old {{{get_query_set}}} normally just calls {{{get_full_query_set}}} and can be overridden in a usual way. This part is backwards compatible. Also managers acquire a new method {{{get_full}}} which works like {{{get}}} but explicitly calls {{{get_full_query_set}}}. This method is used to access single related (parent) objects. This will require users who was overriding {{{get}}} to override {{{get_full}}} instead '''if''' they wish to ensure that default filtering doesn't get in the way. This is as backwards incompatible as was after #7666 that has broken overriding of {{{get}}} but provides a new API to overcome this."		closed	Database layer (models, ORM)	dev		duplicate			Unreviewed	1	0	0	0	0	0