#33450: Integer primary key is wrongly casted to UUID when filtering
GenericRelation on model with UUID primary key.
-------------------------------------+-------------------------------------
Reporter: Santos Gallegos | Owner: Abhinav
| Yadav
Type: Bug | Status: assigned
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Abhinav Yadav):
I have been working on this issue for a while, trying to understand it,
but I'm unable to figure out how django is working internally to answer a
question raised by Mariusz Felisiak in
[https://github.com/django/django/pull/15397/files#r804396962/ this
comment] asking why `self.lhs.output_field` points
`generic_relations.TIntegration.tags` and not to
`generic_relations.TIntegration`. I tried debugging and checking the
variables in related_lookups.py but to no avail.
Any suggestions on where to proceed so as to fix this bug? The patch
provided for this issue seems to work by reversing the fields but I
suppose it's not the expected behaviour to begin with?
--
Ticket URL: <https://code.djangoproject.com/ticket/33450#comment:9>
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/010701838e9b51eb-6698cd80-a505-4389-bb09-7da4484bae34-000000%40eu-central-1.amazonses.com.
