Hi,

I guess it's just about crafting proper SQL for Oracle to do proper introspection and do a PR to be inline with other backends what comes to table/view discovery.

On 11.11.2015 14:14, José Tomás Tocino wrote:
So... is this going anywhere?

El lunes, 9 de noviembre de 2015, 17:55:36 (UTC+1), José Tomás Tocino escribió:

        Well maybe extending queries to do that. Wonder is there
        similiar issues with postgresql?


    Nope, I've just tried granting SELECT access to a user and he can
    inspect the tables properly (in postgresql):

        postgres=# CREATE DATABASE permissions;
        CREATE DATABASE
        postgres=# \c permissions;
        You are now connected to database "permissions" as user
        "postgres".
        permissions=# create table foo (id int, name varchar(255));
        CREATE TABLE
        permissions=# GRANT CONNECT ON DATABASE permissions to tester;
        GRANT
        permissions=# GRANT USAGE ON SCHEMA public TO tester;
        GRANT
        permissions=# GRANT SELECT ON foo TO tester;
        GRANT
        permissions=# \q
        (ENV)vagrant@vagrant-ubuntu-trusty-64:~$ ./manage.py inspectdb
        # This is an auto-generated Django model module.
        # You'll have to do the following manually to clean this up:
        #   * Rearrange models' order
        #   * Make sure each model has one field with primary_key=True
        #   * Remove `managed = False` lines if you wish to allow
        Django to create, modify, and delete the table
        # Feel free to rename the models, but don't rename db_table
        values or field names.
        #
        # Also note: You'll have to insert the output of 'django-admin
        sqlcustom [app_label]'
        # into your database.
        from __future__ import unicode_literals

        from django.db import models


        class Foo(models.Model):
            id = models.IntegerField(blank=True, null=True)
            name = models.CharField(max_length=255, blank=True, null=True)

            class Meta:
                managed = False
                db_table = 'foo'


    So there's that


-- 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-develop...@googlegroups.com.
        To post to this group, send email to
        django-d...@googlegroups.com.
        Visit this group at
        http://groups.google.com/group/django-developers
        <http://groups.google.com/group/django-developers>.
        To view this discussion on the web visit
        
https://groups.google.com/d/msgid/django-developers/CAAOwDo7J33ScxGvQ3UZe2HLMLbc1Eim1TPGwqFDap6Xdp%2BJkFw%40mail.gmail.com
        
<https://groups.google.com/d/msgid/django-developers/CAAOwDo7J33ScxGvQ3UZe2HLMLbc1Eim1TPGwqFDap6Xdp%2BJkFw%40mail.gmail.com>.
        For more options, visit https://groups.google.com/d/optout
        <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 <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/9acc3506-6585-4dd6-9463-0d431707e441%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/9acc3506-6585-4dd6-9463-0d431707e441%40googlegroups.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/56433744.6010104%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to