#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
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"76a0b6aa3aa7bd62c2a9ba11306c906047ee7ada" 76a0b6aa]:
{{{#!CommitTicketReference repository=""
revision="76a0b6aa3aa7bd62c2a9ba11306c906047ee7ada"
Refs #36050 -- Fixed OuterRef support for CompositePrimaryKey on Oracle.
Oracle doesn't support native tuple comparison so each as_oracle
implementation
of tuple lookups must also perform right-hand-side sanitization.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36050#comment:11>
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/010701945f280426-f81a5cbf-d296-4e03-9009-666d21d5c16e-000000%40eu-central-1.amazonses.com.
