Make `inspectdb` regression tests introspect a manageable database

[Ramiro Morales]

Currently, the tests in our test suite direct the inspectdb management command calls to examine the 'default' database that will contain the tables corresponding to all the models of the suite being run (they can be hundreds in the case of the full suite).

This makes creating new test cases for the introspection functionality harder that it should because one needs to peruse a gigantic models.py file.

Maybe we can add a third DB to the DATABASES setting used for our tests and direct/restrict the models in regressiontests/inspectdb/models.py to such DB by using a router?.

[Ramiro Morales]

(s/syncdb/inspectdb/g in ticket summary and description).

[Ramiro Morales]

Fixed in [72130385bfe503bd440e52605c44a10a0480a25b].

[jacobwegner@…]

I think it would be useful to refactor the table_name_filter as part of the management command...perhaps something like

manage.py inspect db --table_name_starts_with=Audit

or

manage.py inspect db --table_name_starts_with=Audit --table_name_exact=AuditLog

Is this worth considering? If so, I will work on a patch.

If the filter really is only meant for tests and it doesn't seem useful to anyone else to expose it as part of the management command "proper", I'll drop it.

[Tim Graham]

Jacob, I suggest creating a new ticket rather than commenting on a closed one.