﻿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
24753	Reverse FK conditions filter queryset when used in case statements in some cases	Matt d'Entremont	nobody	"I'm running into some odd behaviour with the new conditional support added in 1.8.

My use case is the following:

- Annotate a queryset with the count of reverse FKs, matching a condition

This works fine given a many-to-one relationship, however not with many-to-one/none.

With the many-to-one/none, it appears an INNER JOIN is made, which removes objects from my queryset which an empty reverse FK set.

To summarize:

Expected:
Annotate all objects with the a count of reverse FKs matching a condition

Actual:
Annotate only objects objects with 1 or more associated reverse FKs, with a count of the reverse FKs matching a condition"	Bug	closed	Database layer (models, ORM)	1.8	Release blocker	duplicate			Accepted	0	0	0	0	0	0
