#28774: Use only a specific database schema instead of 'public' one (like in
Postgresql)
-------------------------------------+-------------------------------------
Reporter: Riccardo Campisano | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: django, orm, | Triage Stage:
database, postgresql, schema | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => duplicate
Comment:
Official support for database schemas is discussed in #6148.
I think the `'-c search_path=qlf_schema'` method you mentioned uses a
psycopg2 configuration option and I wouldn't expect that to stop working
unless psycopg2 changes it.
--
Ticket URL: <https://code.djangoproject.com/ticket/28774#comment:1>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.046573a679ff58cbde143ae9b3fdfc6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.