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
14766	ordering by a field that does not exists returns an empty QuerySet	Rob Hudson	nobody	If you `.order_by('field_that_does_not_exist')` and evaluate it you get an empty list.  This can lead to bugs if you mistype the field name and wondering why you are getting no results.  I would expect Django to raise an exception instead.  It appears it the queryset doesn't even trigger a database call.	Bug	closed	Database layer (models, ORM)	1.2	Normal	duplicate	sprintdec2010 order_by		Accepted	1	0	0	1	0	0