On 05.11.2015 09:54, José Tomás Tocino García wrote:
In my opinion current behavior is just fine.
How is it "just fine" if there are usecases (the one I've described,
for instance) where the current behavior evidently doesn't cut it?
Well first, inspectdb does only processes tables. As I understood your
case involves views which are not traversed by Django.
Secondly, how often inspectdb is required to run with just a subset?
Tim' suggestion is quite nice (wildcarded query).
Then we hit edge cases, since Django models by default are read/write
how should select-only tables (or views if such behavior is implemented)
should be handled? Should there be overridden methods that tries to
disable invalid actions?
Now we hit another thing. If you do have spatial fields your schema will
get temporary spatial objects, MDRT_*. Then usecase would be getting all
other except those MDRT_* tables (or maybe exclude all tables having *$*)
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 a topic in
the Google Groups "Django developers (Contributions to Django
itself)" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/django-developers/CuczZovhp74/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to django-developers+unsubscr...@googlegroups.com
<mailto:django-developers%2bunsubscr...@googlegroups.com>.
To post to this group, send email to
django-developers@googlegroups.com
<mailto: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/563B087F.3090607%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
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
<mailto:django-developers+unsubscr...@googlegroups.com>.
To post to this group, send email to
django-developers@googlegroups.com
<mailto: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/CAAOwDo5ACkgXcwig1dpd4u_mdDPCe9gvfNyHue%2BbyNaN1n-qog%40mail.gmail.com
<https://groups.google.com/d/msgid/django-developers/CAAOwDo5ACkgXcwig1dpd4u_mdDPCe9gvfNyHue%2BbyNaN1n-qog%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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/563B1348.1010608%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
