#36431: values() query on ForeignObject discards additional columns
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner:
| JaeHyuckSa
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: CompositePrimaryKey | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* severity: Normal => Release blocker
* version: 4.2 => 5.2
Comment:
Marking as a release blocker for 5.2, even though the issue has existed
within `ForeignObject` for longer, since in 5.2
[https://docs.djangoproject.com/en/5.2/topics/composite-primary-key
/#composite-primary-keys-and-relations we've opted to start documenting]
`ForeignObject`'s usage with `CompositePrimaryKey` (whereas before
`ForeignObject` was not documented/public)
--
Ticket URL: <https://code.djangoproject.com/ticket/36431#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/01070198f100d13f-b29c64bc-8b76-46c9-81e6-0be9582281ab-000000%40eu-central-1.amazonses.com.
