#30477: Filtering on reverse ForeignKey relation uses get_db_prep_value from a
wrong field
-------------------------------------+-------------------------------------
Reporter: Michal | Owner: nobody
Petrucha |
Type: Bug | Status: new
Component: Database | Version: master
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Let's start off with a minimal test case.
{{{
from django.db import models
class Local(models.Model):
id = models.DateTimeField(primary_key=True, auto_now_add=True)
class Remote(models.Model):
fk = models.ForeignKey(Local, on_delete=models.CASCADE)
}}}
and
{{{
from django.test import TestCase
from . import models
class ReverseFilterTestCase(TestCase):
def setUp(self):
self.local = models.Local.objects.create()
self.remote = models.Remote.objects.create(fk=self.local)
def test_reverse_filter(self):
obj = models.Local.objects.filter(remote=self.remote).get()
self.assertEqual(obj, self.local)
def test_reverse_filter_direct_field_reference(self):
obj = models.Local.objects.filter(remote__pk=self.remote.pk).get()
self.assertEqual(obj, self.local)
}}}
I would expect both tests to have the same result. However, what happens
is that `test_reverse_filter` fails with the following exception:
{{{
======================================================================
ERROR: test_reverse_filter
(reverse_fk_test_case.tests.ReverseFilterTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/koniiiik/env-
django/reverse_fk_test_case/reverse_fk_test_case/tests.py", line 12, in
test_reverse_filter
obj = models.Local.objects.filter(remote=self.remote).get()
File "/home/koniiiik/repos/git/django/django/db/models/query.py", line
408, in get
num = len(clone)
File "/home/koniiiik/repos/git/django/django/db/models/query.py", line
258, in __len__
self._fetch_all()
File "/home/koniiiik/repos/git/django/django/db/models/query.py", line
1240, in _fetch_all
self._result_cache = list(self._iterable_class(self))
File "/home/koniiiik/repos/git/django/django/db/models/query.py", line
57, in __iter__
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch,
chunk_size=self.chunk_size)
File "/home/koniiiik/repos/git/django/django/db/models/sql/compiler.py",
line 1068, in execute_sql
sql, params = self.as_sql()
File "/home/koniiiik/repos/git/django/django/db/models/sql/compiler.py",
line 481, in as_sql
where, w_params = self.compile(self.where) if self.where is not None
else ("", [])
File "/home/koniiiik/repos/git/django/django/db/models/sql/compiler.py",
line 397, in compile
sql, params = node.as_sql(self, self.connection)
File "/home/koniiiik/repos/git/django/django/db/models/sql/where.py",
line 81, in as_sql
sql, params = compiler.compile(child)
File "/home/koniiiik/repos/git/django/django/db/models/sql/compiler.py",
line 397, in compile
sql, params = node.as_sql(self, self.connection)
File
"/home/koniiiik/repos/git/django/django/db/models/fields/related_lookups.py",
line 130, in as_sql
return super().as_sql(compiler, connection)
File "/home/koniiiik/repos/git/django/django/db/models/lookups.py", line
162, in as_sql
rhs_sql, rhs_params = self.process_rhs(compiler, connection)
File "/home/koniiiik/repos/git/django/django/db/models/lookups.py", line
257, in process_rhs
return super().process_rhs(compiler, connection)
File "/home/koniiiik/repos/git/django/django/db/models/lookups.py", line
94, in process_rhs
return self.get_db_prep_lookup(value, connection)
File "/home/koniiiik/repos/git/django/django/db/models/lookups.py", line
186, in get_db_prep_lookup
[get_db_prep_value(value, connection, prepared=True)]
File
"/home/koniiiik/repos/git/django/django/db/models/fields/related.py", line
942, in get_db_prep_value
return self.target_field.get_db_prep_value(value, connection,
prepared)
File
"/home/koniiiik/repos/git/django/django/db/models/fields/__init__.py",
line 1429, in get_db_prep_value
return connection.ops.adapt_datetimefield_value(value)
File
"/home/koniiiik/repos/git/django/django/db/backends/sqlite3/operations.py",
line 218, in adapt_datetimefield_value
if timezone.is_aware(value):
File "/home/koniiiik/repos/git/django/django/utils/timezone.py", line
248, in is_aware
return value.utcoffset() is not None
AttributeError: 'int' object has no attribute 'utcoffset'
----------------------------------------------------------------------
}}}
The problem is that when compiling a `RelatedExact` node to SQL, the rhs
is processed with `get_db_prep_value` of the `ForeignKey` field, which
defers to the target field, which in this case is the primary key of the
local model. However, the correct field to process the value would be the
remote primary key field.
FWIW, the lhs gets compiled to the correct SQL expression,
`"reverse_fk_test_case_remote"."id"`. The difference appears to be that
when compiling the lhs, the `Col`'s `target` attribute is used, which is a
reference to the primary key of the remote model, but when processing the
rhs, the `output_field` attribute of the lhs is used instead, which is a
reference to the `ForeignKey` field.
Unfortunately, I don't quite understand all of the logic here, but it
seems to me that whenever the lhs is a `Col` instance, the correct field
to use would be `target`, and in other cases, i.e. results of more complex
expressions, it would be `output_field`. I'm just guessing here, though,
but at least a quick run through the test suite with a modified
`django.db.models.lookups.FieldGetDbPrepValueMixin` seems to agree, though
I don't really find that to be sufficient evidence. At the same time, I
don't really get why `output_field` and `target` reference different
fields in this case; could be that that is the root cause.
--
Ticket URL: <https://code.djangoproject.com/ticket/30477>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.4b7e6e9bf6d32a8e9036f1d7da2bf34c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
