#30477: Filtering on reverse ForeignKey relation uses get_db_prep_value from a
wrong field.
-------------------------------------+-------------------------------------
Reporter: Michal Petrucha | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* stage: Unreviewed => Accepted
Comment:
Thanks for this report. I was able to reproduce this issue on all backends
except PostgreSQL. It looks that using foreign keys to models with custom
primary keys that require preparing DB value is not a common use case.
Reproduced at 7619a33665ccc138c1583a2cce5a5de6d86c9cb4.
--
Ticket URL: <https://code.djangoproject.com/ticket/30477#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 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/066.4b74d41277b7701a4f196cf6c5575426%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
