Opened 9 years ago
Closed 9 years ago
#25658 closed New feature (fixed)
Add an optional positional argument to inspectdb to allow choosing what table/views should be inspected
| Reported by: | JoseTomasTocino | Owned by: | JoseTomasTocino |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | dev |
| Severity: | Normal | Keywords: | inspectdb |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Comes from this discussion: https://groups.google.com/forum/#!topic/django-developers/CuczZovhp74
It would be great to be able to manually choose what table and/or views should be inspected when using the inspectdb command, specially in situations where readable table/views are not properly reported by the DB.
Here's a pull request with my proposed solution: https://github.com/django/django/pull/5530
Change History (6)
comment:1 by , 9 years ago
| Has patch: | set |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:2 by , 9 years ago
| Component: | Database layer (models, ORM) → Core (Management commands) |
|---|---|
| Needs documentation: | set |
| Triage Stage: | Unreviewed → Accepted |
| Version: | 1.8 → master |
comment:3 by , 9 years ago
| Needs documentation: | unset |
|---|
comment:4 by , 9 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
I think #14098 should solve this use case. Tables which can't be introspected will now be skipped.
comment:5 by , 9 years ago
| Resolution: | wontfix |
|---|---|
| Status: | closed → new |
Now I realized the problem isn't that the table can't be introspected but that it's not returned by the existing introspection query on Oracle. So we either need to revise that query or accept this feature.
Added docs and release notes in the pull request.