#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
-------------------------------------+-------------------------------------
Comment (by Michal Petrucha):
FWIW, the way I discovered this was with a UUID primary key with a
Postgres backend, which might not be ''that'' unusual, but in Django 1.11.
However, I had to reproduce it with a different field on master, because
`UUIDField.to_python` has become a bit less strict since 1.11, and it
doesn't error out on integers anymore.
--
Ticket URL: <https://code.djangoproject.com/ticket/30477#comment:2>
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.243bc91ead531d699de23c9c44a90a44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
