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
1730	[patch] ORM shouldn't add table prefix for a custom SELECT column	Cheng Zhang <czhang.cmu+web@…>	Adrian Holovaty	"For code like this:
{{{
from mysite.polls.models import Poll, Choice
from django.db import connection

select = {
 'choices': 'SELECT COUNT(*) FROM polls_choice WHERE poll_id=polls_poll.id',
}
p = Poll.objects.extra(select=select).order_by('choices')
try:
	print ""p="", p
except:
	pass
print ""db.queries=%s"" % connection.queries
}}}

The ORM generates SQL statement as:
{{{
SELECT ""polls_poll"".""id"",""polls_poll"".""question"",""polls_poll"".""pub_date"",
(SELECT COUNT(*) FROM polls_choice WHERE poll_id=polls_poll.id) AS ""choices""
FROM ""polls_poll"" ORDER BY ""polls_poll"".""choices"" ASC
}}}

That's incorrect. The correct statement should be:
{{{
SELECT ""polls_poll"".""id"",""polls_poll"".""question"",""polls_poll"".""pub_date"",
(SELECT COUNT(*) FROM polls_choice WHERE poll_id=polls_poll.id) AS ""choices""
FROM ""polls_poll"" ORDER BY ""choices"" ASC
}}}

A patch will follow."	defect	closed	Database layer (models, ORM)	dev	normal	duplicate			Unreviewed	1	0	0	0	0	0