#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 akaariai):
I agree on simplifying the Oracle hacks in the patch. The current patch
tries to abstract too much of the differences between the databases away.
Lets rip the current patch to absolute minimum, and then continue from
there.
The "multiple schemas on Oracle -> multiple defined connections" needs
some more thought on how to map the tables to the connections, and how to
see that some aliases are just schemas for another alias, so that joins
are allowed, and one can save model in schema "other" using the default
connection. I hope this can be made to work...
--
Ticket URL: <https://code.djangoproject.com/ticket/6148#comment:117>
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.
