>
> In that case, are you sure what you're offering is a solution and not just
> a
> workaround? Shouldn't we make it so that inspectdb always gets all the
> tables
> in the schema?
>

Well, as far as I'm concerned, I'd rather be able to choose what tables I
want to work with. In fact, I'm not sure it's possible to know all the
accessible tables/views for a single user in Oracle — at least in a way
that doesn't return a myriad of built-in tables and views unrelated to my
needs.


> >
> > My intention is just that, to be able to limit what tables are
> introspected
> > when inspectdb is launched, regardless of what has been inspected before.
> >
>
> What do you thunk of Tim Allen's suggestion:
>
>         ./manage.py inspectdb --tables=form_*,user_*
>
>
Well, inspectdb already does that. There's a shadow option
called table_name_filter that is used by tests and does exactly that,
filter the tables/views according to a given filtering function (usually
one that checks whether the name starts with a string). The only problem is
that it's not available to be used from the manage.py command line, because
it needs you to use Python to write the filtering function. For example:

        call_command('inspectdb',
                     table_name_filter=lambda tn:
tn.startswith('inspectdb_'),
                     stdout=out)

In the tests, the table_name_filter option is always filled with a function
that checks the beginning of the table name.

The suggestion is certainly interesting and kind of goes hand in hand with
mine. The problem I still see is what I mentioned before: how to get all
the views and tables that can be read by the user so you can filter them.
These are two different beasts I'm afraid.

Regards.


-- 
José Tomás Tocino García
http://www.josetomastocino.com

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAAOwDo5Ouabie7KeO17tRMmChuT2ZdfJjK9BO%3DfYhmsczsUP1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to