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
25569	Add a friendly error report when using select_related() on a reverse relation	Shai Berger	Vincent Perez	"Since 1.8, if you refer to a non-existent field in `select_related()`, you get an error where the code used to pass silently. One potentially common source for such errors is attempts to use `select_related()` on reverse relations -- up to 1.7, this would have seemed to work, with 1.8 it breaks.

I think it would be friendlier to users upgrading from (<=) 1.7 if the error report called this situation out explicitly, rather than referring to reverse relations as ""non-existent"".

Not sure if this merits a backport to 1.8.x -- on the one hand, it doesn't really fall under the criteria, on the other hand, I think it would be very useful and many people will be coming over to 1.8 and stay there, and the validation of `select_related()` itself is a new feature in 1.8."	New feature	closed	Database layer (models, ORM)	1.8	Normal	wontfix			Accepted	1	0	0	0	0	0