#34015: "Related Field got invalid lookup: startswith" on CharField ForeignKey
-------------------------------------+-------------------------------------
Reporter: Thomas | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: ORM lookup | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Thomas):
@Mariusz Felisiak: Thanks for the heads-up, I hadn't found that ticket in
my searches.
@Alex Morega: Thank you. I should have checked the SQL of my example for
the join. I relied on my findings on my existing code base which uses
`parent_object__object_id__startswith` to circumvent the RelatedField
lookup problem. I have the join there but it must be coming from somewhere
else.
--
Ticket URL: <https://code.djangoproject.com/ticket/34015#comment:6>
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/01070183455b254b-8604a7d1-0b98-4a75-8299-090ce8c51b04-000000%40eu-central-1.amazonses.com.