Opened 8 years ago

Closed 7 years ago

#9871 closed (fixed)

MyModel.object.values('mygeometryfield') doesn't work

Reported by: denis@… Owned by: nobody
Component: GIS Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


I expected a result in the form of [{'mygeometryfield' : a_geom_instance}, ...] but got a [{'mygeometryfield' : 'WKBSTR'},...] instead.

Change History (3)

comment:1 Changed 8 years ago by anonymous

  • milestone post-1.0 deleted

Milestone post-1.0 deleted

comment:2 Changed 7 years ago by Alex

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Design decision needed

Moving to DDN, it's generally been said that values() is expected to return the raw DB values(such as with ForeignKeys).

comment:3 Changed 7 years ago by jbronn

  • Resolution set to fixed
  • Status changed from new to closed

(In [10326]) Fixed #9871 -- Geometry objects are now returned in dictionaries and tuples returned by values() and values_list(), respectively; updated GeoQuery methods to be compatible with defer() and only; removed defunct GeomSQL class; and removed redundant logic from Query.get_default_columns.

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