#6148: Add generic support for database schemas
-------------------------------------+-------------------------------------
Reporter: Ian Kelly | Owner: Anssi
| Kääriäinen
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle postgresql | Triage Stage: Accepted
mysql schemas |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Christian González):
Is there any chance supporting Oracle too? I have exactly this use case:
Using a different (read-only) Oracle user to access a production database
read-only. This user gets his own schema, and I have to grant access to
the production schema too using Oracle. Now I plan to create a REST API
using Django/DRF for this (proprietary) database - but I would have to add
the schema to every Meta.db_table in each model.
It would be convenient to have something like a SCHEMA setting in
DATABASES working for Oracle too.
I think I'm not capable of providing a production quality patch for Django
myself, just maybe help a bit.
As stated before - should this be discussed in a separate ticket?
--
Ticket URL: <https://code.djangoproject.com/ticket/6148#comment:181>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.11a7612a09c7f79c5607701b0527ef29%40djangoproject.com.
