#6148: Add generic support for database schemas
-------------------------------------+-------------------------------------
Reporter: ikelly | Owner: akaariai
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Design
Keywords: oracle postgresql | decision needed
mysql schemas | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by bruth):
@akaariai Thanks for the patch! I have a project where I have multiple
schemas and some of the tables have foreign keys between them. My
environment consists of PostgreSQL and my settings contain multiple
entries in ``DATABASES`` with their own schema defined (as suppose to
hard-coded schemas in the model ``Meta`` classes). I ran the ``./manage.py
sqlall`` command and noticed a couple things:
- there are redundant ``CREATE SCHEMA`` statements before each ``CREATE
TABLE``
- foreign keys to tables from other schemas do not output the correct
schema
--
Ticket URL: <https://code.djangoproject.com/ticket/6148#comment:121>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
