Opened 17 years ago

Closed 16 years ago

#4358 closed (fixed)

Inconsistent results between .values() and .values('field') when field is an fkey

Reported by: Collin Grady <cgrady@…> Owned by: nobody
Component: Database layer (models, ORM) Version: dev
Severity: Keywords: qs-rf-fixed
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

In a model with a ForeignKey, (say Choice from the poll example), Choice.objects.values() will show one field as 'poll_id' for the ForeignKey.

However, if you want to select only that value, Choice.objects.values('poll_id') will raise FieldDoesNotExist. Instead it requires you to do Choice.objects.values('poll') and returns the values in the key 'poll'

Change History (6)

comment:1 by Simon G. <dev@…>, 17 years ago

Triage Stage: UnreviewedDesign decision needed

comment:2 by Malcolm Tredinnick, 17 years ago

Keywords: qs-rf added

comment:3 by Malcolm Tredinnick, 16 years ago

(In [6516]) queryset-refactor: Made the use of values() for ForeignKey fields consistent
and documented this feature. Refs #4358.

comment:4 by Malcolm Tredinnick, 16 years ago

Keywords: qs-rf-fixed added; qs-rf removed

comment:5 by Malcolm Tredinnick, 16 years ago

Triage Stage: Design decision neededAccepted

comment:6 by Malcolm Tredinnick, 16 years ago

Resolution: fixed
Status: newclosed

(In [7477]) Merged the queryset-refactor branch into trunk.

This is a big internal change, but mostly backwards compatible with existing
code. Also adds a couple of new features.

Fixed #245, #1050, #1656, #1801, #2076, #2091, #2150, #2253, #2306, #2400, #2430, #2482, #2496, #2676, #2737, #2874, #2902, #2939, #3037, #3141, #3288, #3440, #3592, #3739, #4088, #4260, #4289, #4306, #4358, #4464, #4510, #4858, #5012, #5020, #5261, #5295, #5321, #5324, #5325, #5555, #5707, #5796, #5817, #5987, #6018, #6074, #6088, #6154, #6177, #6180, #6203, #6658

Note: See TracTickets for help on using tickets.
Back to Top