It's actually quite common pattern in Oracle to create tables using
special admin user and then create separate users that just do have
spesific priviledges per table.
Specially old Oracle docs promoted such a pattern.
In my opinion current behavior is just fine. Also I think inspectdb
doesn't actually see any views, just tables.
On 04.11.2015 18:26, Shai Berger wrote:
On Wednesday 04 November 2015 16:46:35 José Tomás Tocino García wrote:
Are you doing something like "inspectdb other.a other.b" or "inspectdb a
b"?
The latter. Given a single database (and the default schema), my patch
allows to just inspect tables "a" and "b".
Now I get it. There are tables in your schema, which are not owned by you.
Frankly, I wasn't aware this was possible.
The problem is what I mentioned in my first message, the current
implementation of inspectdb fails to get all the tables and views when the
user does not own them.
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?
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_*
Thanks for your patience in this,
Shai.
--
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 [email protected].
To post to this group, send email to [email protected].
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/563B087F.3090607%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
