#31940: Order of WHERE clauses do not match the order of the arguments to
.filter()
-------------------------------------+-------------------------------------
Reporter: Tommy Li | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: 3.0
layer (models, ORM) |
Severity: Normal | Keywords: orm
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
With the following sample model
{{{#!python
class MyModel(models.Model):
a_field = models.IntegerField()
b_field = models.IntegerField()
}}}
If I run the following query:
{{{#!python
MyModel.objects.filter(b_field = 1, a_field = 2)
}}}
the SQL that it generates is
{{{
SELECT "mymodel"."a_field", "mymodel"."b_field
FROM "mymodel"
WHERE ("mymodel"."a_field" = 2 AND "mymodel"."b_field" = 1)
}}}
I would expect the order of the clauses in the WHERE statement to match
the order of arguments passed to the filter statement. In my case,
`b_field` has a much higher cardinality than `a_field` and I want the
query to use an index I have on `(b_field, a_field)`
After some experimentation, it looks like the WHERE clauses are ordered
alphabetically by column name. Is that explicitly intended, or is it just
a side effect of some implementation detail?
--
Ticket URL: <https://code.djangoproject.com/ticket/31940>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.9d91bbc551f10a192c4590a3faed4c12%40djangoproject.com.
