#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):
I agree, the one issue with ''only'' using a router is the lack of
transparency of which schemas are ''in use'' or are available. I had
thought about defining multiple database entries for each schema also, but
it got a bit unwieldy and it kind of conceptually conflicts with the fact
that cross-schema references are possible (at least in postgres).
Thanks for the quick review. I will am going to get the tests up-to-date
at the very least and then continue musing over where/how to explicitly
define the schemas in the settings.
--
Ticket URL: <https://code.djangoproject.com/ticket/6148#comment:128>
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.
