Opened 17 years ago

Closed 17 years ago

#10836 closed (fixed)

FieldDoesNotExist import in gis.db.models.sql.query should be in gis.db.models.sql.where

Reported by: Sean Legassick Owned by: nobody
Component: GIS Version: dev
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Self-explanatory - the import of FieldDoesNotExist is in the wrong file - the exception isn't raised anywhere in sql/query.py but it is in sql/where.py (in _check_geo_field). I'm guessing this was due to some code re-organization.

Attachments (1)

10836-fielddoesnotexist-import-in-correct-module.diff​ (1.0 KB ) - added by Sean Legassick 17 years ago.

Download all attachments as: .zip

Change History (2)

by Sean Legassick, 17 years ago

Attachment: 10836-fielddoesnotexist-import-in-correct-module.diff​ added

comment:1 by Alex Gaynor, 17 years ago

Resolution: → fixed
Status: new → closed

Fixed in r10572.

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