#26667: Invalid query for OneToOneField if 'to_field' specified and
primary_key=True
-------------------------------------+-------------------------------------
Reporter: kwist | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: OneToOneField | Triage Stage: Accepted
to_field primary_key |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"e2296e7f0acf9c50868ab997ba565c1f47beb45b" e2296e7f]:
{{{
#!CommitTicketReference repository=""
revision="e2296e7f0acf9c50868ab997ba565c1f47beb45b"
Fixed #26667 -- Fixed a regression in queries on a OneToOneField that has
to_field and primary_key=True.
Thanks Simon Charette for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26667#comment:4>
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/063.a9e55d47bb653b2b0d7256af10dcbdd9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
