#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)
Change History (10)
by , 17 years ago
| Attachment: | geowherenode_expressions_fix.diff added |
|---|
comment:1 by , 17 years ago
| Needs documentation: | set |
|---|---|
| Needs tests: | set |
by , 17 years ago
| Attachment: | geowherenode_expressions_fix_v2.diff added |
|---|
comment:2 by , 17 years ago
This current patches don't take into account if the geometry fields are in different SRIDs, d'oh.
by , 17 years ago
| Attachment: | geowherenode_expressions_fix_v3.diff added |
|---|
Now takes into account different SRIDs.
comment:4 by , 17 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:5 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:6 by , 17 years ago
| milestone: | → 1.1 |
|---|
Note:
See TracTickets
for help on using tickets.
Fix, tests, and some cleanup.