#12637 closed (fixed)
GeoDjango's `inspectdb` command is broken
| Reported by: | jbronn | Owned by: | jbronn |
|---|---|---|---|
| Component: | GIS | Version: | 1.1 |
| Severity: | Keywords: | gis inspectdb introspection | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
GeoDjango overrides the inspectdb command, and was not updated when multi-db was merged into trunk (e.g., it still references SpatialBackend which no longer exists). In addition, inspectdb is almost copied verbatim -- and does not apply DRY. The command should be fixed, and should subclass the original command so that further updates will not necessitate re-copying the entire code.
Change History (3)
comment:1 by , 15 years ago
| Status: | new → assigned |
|---|
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [12257]) Fixed #12637 -- GeoDjango's
inspectdbcommand is now a subclass of Django's, and works with all spatial backends (Oracle and SpatiaLite did work before). This changeset introduces new introspection modules for all of the spatial backends and adds hooks to the originalinspectdb.Commandclass to enable reuse.