#6148: Add generic support for database schemas
---------------------------------------------------+------------------------
Reporter: ikelly | Owner:
Status: new | 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 ikelly):
Since this ticket has been seeing some activity lately, I decided to put
some work in on the patch. The old patch worked by fudging the schema
into the db_table attribute, which is sort of a hack. I've changed it to
combine db_schema and db_table into an entirely new attribute,
qualified_name.
I've also fixed up a number of areas that were still passing around raw
table names, including I think the case that oldium pointed out. Finally,
I've made the necessary changes in the Oracle backend to get this to work.
I'm not too keen on dropping MySQL support just because it's difficult to
test. To the end-user, Django is not in the business of creating and
dropping schemas, and so it shouldn't matter what a schema actually
represents as long as we can reference the tables inside it. Testing is
also complicated in Oracle where "schema" is basically synonymous with
"user", and I don't have the test fully working yet there either.
--
Ticket URL: <http://code.djangoproject.com/ticket/6148#comment:23>
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
-~----------~----~----~----~------~----~------~--~---
