#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 layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: orm | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Tommy Li:
Old description:
> 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?
New description:
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?
A workaround is to run
{{{#!python
MyModel.objects.filter(b_field = 1).filter(a_field = 2)
}}}
But this is pretty inconvenient if you just want to run a .get, you would
have to build out a verbose .filter().filter().first() query
--
--
Ticket URL: <https://code.djangoproject.com/ticket/31940#comment:1>
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/066.11af38f3014d70b94e25a2e400d38371%40djangoproject.com.
