On Tue, Mar 22, 2011 at 9:49 PM, Brian Neal <[email protected]> wrote: > I studied the SQL that Django generated and it seemed fine to me. > That's why I wonder if it is a MySQL issue since the EXPLAIN said it > had a possible key (PRIMARY) but then ended up not using it (bottom > one):
that's because it saw so few rows (just 15) that it was cheaper to scan the whole thing instead of using the index -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
