On Thu, May 22, 2014 at 3:33 AM, Fabio Caritas Barrionuevo da Luz <
bna...@gmail.com> wrote:

> *Django not provides way to use inspectdb in a postgresql schema with name
> different of "public"*
>
> If you think this is an important feature and should be included in
> django, Please send your considerations and use cases to the topic:
>
> https://groups.google.com/forum/#!topic/django-developers/lSHrDFZM4lQ
>
> If you do not know the concept of postgresql schema, please read:
>
> ​http://www.postgresql.org/docs/9.3/static/ddl-schemas.html
>
> This is an especially useful feature if you have to deal with the legacy
> database and perhaps also for multiple-tenant
>
> This is a feature requested for 8 years[1][2].
>

To provide some perspective here -- there's no shortage of people who have
expressed an interest in this idea. What we're missing is someone to write
the code. #6148 was on the 'intended feature list' for several releases
(back when we had an intended feature list as part of our release process),
but the patch never got to a point of maturity that would allow it to be
merged into master.

So - yes, this is a worthy feature. If a working, tested, documented patch
were available, it would probably find its way into trunk reasonably
quickly. What we don't have is that patch. We need someone from the
community to contribute such a patch.

Yours,
Russ Magee %-)

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

Reply via email to