#36050: Cannot resolve OuterRef to CompositePrimaryKey
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Csirmaz
| Bendegúz
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: subquery | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"8bee7fa45cd7bfe70b68784314e994e2d193fd70" 8bee7fa4]:
{{{#!CommitTicketReference repository=""
revision="8bee7fa45cd7bfe70b68784314e994e2d193fd70"
Fixed #36050 -- Added OuterRef support to CompositePrimaryKey.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36050#comment:10>
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 visit
https://groups.google.com/d/msgid/django-updates/01070194506fd2f9-0aa87260-81c0-4d51-84a2-3cf74d67f79a-000000%40eu-central-1.amazonses.com.
