#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 ikelly):
Replying to [comment:139 bruth]:
> I just noticed your comment `# Or, to mirror the production schemas,
just do:`.. that should be the default, so it does not need to be defined
explicitly.
I'm going to disagree and advocate that this option not even be explicitly
supported. It's bad enough already that the Oracle backend runs tests on
the production-configured database (just in a different tablespace and
schema). If you don't use a separate settings.py file with separate
connection information for testing, and you mirror the production schemas,
then your tests are actually going to run in your production schemas.
The other thing I want to comment on is that SCHEMA_MAP should be
completely optional, unless you're running syncdb and have managed tables
in those schemas. For day-to-day operation, Django should only be
connecting as the Django user and does not need full authentication
information for other schemas.
--
Ticket URL: <https://code.djangoproject.com/ticket/6148#comment:143>
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 https://groups.google.com/groups/opt_out.
