Opened 15 years ago

Closed 15 years ago

Last modified 12 years ago

#10159 closed (fixed)

Fix F() expressions to work on geographic fields.

Reported by: jbronn Owned by: jbronn
Component: GIS Version: dev
Severity: Keywords: gis expression where
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: yes
Needs tests: yes Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Currently, users will receive a TypeError when trying to use a F() expression on geographic field. The attached patch is a preliminary fix and needs tests.

Attachments (3)

geowherenode_expressions_fix.diff (1.7 KB ) - added by jbronn 15 years ago.
geowherenode_expressions_fix_v2.diff (8.1 KB ) - added by jbronn 15 years ago.
Fix, tests, and some cleanup.
geowherenode_expressions_fix_v3.diff (16.1 KB ) - added by jbronn 15 years ago.
Now takes into account different SRIDs.

Download all attachments as: .zip

Change History (10)

by jbronn, 15 years ago

comment:1 by jbronn, 15 years ago

Needs documentation: set
Needs tests: set

by jbronn, 15 years ago

Fix, tests, and some cleanup.

comment:2 by jbronn, 15 years ago

This current patches don't take into account if the geometry fields are in different SRIDs, d'oh.

by jbronn, 15 years ago

Now takes into account different SRIDs.

comment:3 by (none), 15 years ago

milestone: post-1.0

Milestone post-1.0 deleted

comment:4 by Alex Gaynor, 15 years ago

Triage Stage: UnreviewedAccepted

comment:5 by jbronn, 15 years ago

Resolution: fixed
Status: newclosed

(In [9963]) Fixed #10159 -- F() expressions now work on geographic fields. The tests are in relatedapp, which has been retrofitted to work with Oracle (minus the prior offending tests). I'm back.

comment:6 by jbronn, 15 years ago

milestone: 1.1

comment:7 by Jacob, 12 years ago

milestone: 1.1

Milestone 1.1 deleted

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