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
11003	Add USE INDEX, FORCE INDEX capabilities to ORM	Renato Alves	nobody	"Recently I've add significant performance issues with Django + MySQL.
The reasons behind this are MySQL not using an existing index due to low cardinality and instead do a full table scan. In most cases this is the correct choice but there some exceptions. For these, the workaround is to add ""FORCE INDEX (index_name)"" to the SQL.
However there is no support for this feature in the ORM.

As for the relevance of this functionality, in my case, query time was 0.09 sec when using FORCE INDEX and 10.3 sec when not.
This problem becomes more visible if the columns involved are used in several JOIN operations."	Uncategorized	closed	Database layer (models, ORM)	dev	Normal	wontfix	INDEX USE FORCE	clouserw@… rkm Simon Litchfield	Design decision needed	1	0	1	0	0	0