#36431: values() query on ForeignObject discards additional columns -------------------------------------+------------------------------------- Reporter: Jacob Walls | Owner: | JaeHyuckSa Type: Bug | Status: closed Component: Database layer | Version: 5.2 (models, ORM) | Severity: Release blocker | Resolution: fixed Keywords: CompositePrimaryKey | 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 Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed * status: assigned => closed Comment: In [changeset:"bb7a7701b1a0e8fffe14dcebf5d5bac7f176c02a" bb7a770]: {{{#!CommitTicketReference repository="" revision="bb7a7701b1a0e8fffe14dcebf5d5bac7f176c02a" Fixed #36431 -- Returned tuples for multi-column ForeignObject in values()/values_list(). Thanks Jacob Walls and Simon Charette for tests. Signed-off-by: SaJH <wogur981...@gmail.com> }}} -- Ticket URL: <https://code.djangoproject.com/ticket/36431#comment:15> 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 django-updates+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/django-updates/01070198f7526245-fe03e955-cb0f-477d-88c4-03a592ddbab8-000000%40eu-central-1.amazonses.com.