#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 hejsan):
Hi, nice to see that this is finally being worked on.
The most elegant solution from my perspective would be if I could specify
in my project-wide settings that I want to use schemas, and then I would
get a generic schema implementation.
Then the database layer would create a schema for each app, so that
instead of:
- auth_group (table)
- auth_user (table)
- auth_message (table)
- etc...
it would instead create it thus:
- auth (schema)
- group (table)
- user (table)
- message (table)
with the names all shorter and nicer.
But it should also allow per-app or per-model schema option to explicitly
specify what you want to ease support of legacy databases etc.
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
--
Ticket URL: <http://code.djangoproject.com/ticket/6148#comment:32>
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
