#36392: ValueError not raised when wrong number of columns selected by subquery
against composite primary key
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
| Walls
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: pk | 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:"994dc6d8a1bae717baa236b65e11cf91ce181c53" 994dc6d8]:
{{{#!CommitTicketReference repository=""
revision="994dc6d8a1bae717baa236b65e11cf91ce181c53"
Fixed #36392 -- Raised ValueError when subquery referencing composite pk
selects too many columns.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36392#comment:7>
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/01070196d7bfa3c3-315d93bf-d627-49cd-88ab-9b5fe057f54f-000000%40eu-central-1.amazonses.com.
