#22673: inspectdb not support database schema on postgresql with name different
of
"public"
-------------------------------------+-------------------------------------
Reporter: Fabio Caritas | Owner: nobody
Barrionuevo da Luz <bnafta@…> | Status: new
Type: New feature | Version: master
Component: Uncategorized | Resolution:
Severity: Normal | Triage Stage:
Keywords: inspectdb, | Unreviewed
introspection, postgresql, schema | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by andrewgodwin):
As per #6148, Django doesn't actually support schemas, so I'm not sure we
can resolve this until that's fixed.
Schema support is a big task for us and hopefully one we can support soon,
but it's not a quick thing to implement! The only workaround I could think
of would be using set_search_path in initial connection SQL (some comments
on that in the ticket above or google around for how other people have
done it) to make sure the other schema is included and then inspectdb
might see the tables in it.
--
Ticket URL: <https://code.djangoproject.com/ticket/22673#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/109.8537e080919406e81a8f2db2c7ac4e77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
