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
--
Ticket URL: <https://code.djangoproject.com/ticket/25658>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => assigned
* needs_better_patch: => 0
* needs_tests: => 0
* owner: nobody => JoseTomasTocino
* needs_docs: => 0
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/25658#comment:1>
* needs_docs: 0 => 1
* version: 1.8 => master
* component: Database layer (models, ORM) => Core (Management commands)
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/25658#comment:2>
* needs_docs: 1 => 0
Comment:
Added docs and release notes in the pull request.
--
Ticket URL: <https://code.djangoproject.com/ticket/25658#comment:3>
* status: assigned => closed
* resolution: => wontfix
Comment:
I think #14098 should solve this use case. Tables which can't be
introspected will now be skipped.
--
Ticket URL: <https://code.djangoproject.com/ticket/25658#comment:4>
* status: closed => new
* resolution: wontfix =>
Comment:
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/25658#comment:5>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"39a16dd2e003f9ca82a6d061a022ced6904bd243" 39a16dd]:
{{{
#!CommitTicketReference repository=""
revision="39a16dd2e003f9ca82a6d061a022ced6904bd243"
Fixed #25658 -- Allowed inspectdb to inspect a specific set of tables.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25658#comment:6>