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 JoseTomasTocino, 9 years ago

Has patch: set
Owner: changed from nobody to JoseTomasTocino
Status: newassigned

comment:2 by Claude Paroz, 9 years ago

Component: Database layer (models, ORM)Core (Management commands)
Needs documentation: set
Triage Stage: UnreviewedAccepted
Version: 1.8master

comment:3 by JoseTomasTocino, 9 years ago

Needs documentation: unset

Added docs and release notes in the pull request.

comment:4 by Tim Graham, 9 years ago

Resolution: wontfix
Status: assignedclosed

I think #14098 should solve this use case. Tables which can't be introspected will now be skipped.

comment:5 by Tim Graham, 9 years ago

Resolution: wontfix
Status: closednew

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.

comment:6 by Tim Graham <timograham@…>, 9 years ago

Resolution: fixed
Status: newclosed

In 39a16dd:

Fixed #25658 -- Allowed inspectdb to inspect a specific set of tables.

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