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
11459	QuerySet.count() generates invalid sql when used with select_related() and extra(where=[customWhereClause])	eddified	nobody	"Here is the error message:
{{{
(1054, ""Unknown column 'beyondStore_artist.name' in 'where clause'"")
}}}

This is the invalid sql that calling count() is generating that causes the above error message:
{{{
SELECT COUNT(*) FROM `sss_song` WHERE (match(sss_song.title) against('hits')) or (match(sss_artist.name, sss_artist.description) against('hits')) or (match(sss_album.title, sss_album.description) against('hits'))
}}}

Here is the code that generates the QuerySet:
{{{
songs = models.Song.objects.select_related('album__genre__genre__id', 'artist__name').extra(where = [where_clause])
t = songs.count() # sql error is caused by this call to count()
}}}

I know that the query to get the actual data works just fine. It is only the COUNT that is not working. The work around was to get the count manually (by writing an sql statement that gets the count, and executing the statement 'manually' using connection.cursor().execute(sql)).
The two arguments passed to ""select related"" are both valid.

The problem is that the 'where' clause uses the two tables that are specified by the ""select_related"" call, but the count() function apparently ignores the select_related call. 

Perhaps the QuerySet.count() function should be smart enough to take the ""select_related"" args into consideration when generating the COUNT sql.

I did try to specify missing tables using tables=[...] as an argument to extra(), but I couldn't get it to work with both the count() and the actual data query."	Bug	closed	Database layer (models, ORM)	1.3	Normal	wontfix	QuerySet.extra	Jamey Sharp j	Accepted	0	0	0	0	0	0