#6148: Add generic support for database schemas
---------------------------------------------------+------------------------
Reporter: ikelly | Owner: kmpm
Status: assigned | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: oracle
postgresql mysql schemas
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------------------+------------------------
Comment (by oldium):
Replying to [comment:32 hejsan]:
> Is what I am describing what is being worked on, or are you only making
it so that you have to specify for every single model or app that you want
it to live in a schema?
> -thanks
The main purpose of this for me is to have the ''site'' living in the
different namespace, but in the same database (PostgreSQL); not to have
the models/apps in dedicated namespaces. In this way you can run
completely different sites (users, models...) within the same database -
useful if you do not have full control over the database (hosting for
example).
--
Ticket URL: <http://code.djangoproject.com/ticket/6148#comment:37>
Django <http://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
-~----------~----~----~----~------~----~------~--~---
