#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 JorisBenschop):
IMO the reality is that very few people will have schema creation
permissions in Oracle, and if you do, you generally do not want to use
that account to install a Django site with migrations. I think assuming
that the schema exists works fine for Oracle, given that the schema and
test-schema may be set in config (I think part of this functionality
already exists). If not, the resulting error is easy to catch.
--
Ticket URL: <https://code.djangoproject.com/ticket/6148#comment:175>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.332c3d048b3143d46ccbc89c0966d96c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
