Re: [Django] #6148: Add generic support for database schemas

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: [Django] #6148: Add generic support for database schemas

#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
Changes (by František Svoboda):

 * cc: František Svoboda (added)


 I would like to use a different user for migrations and for actual
 application. But both should use the same Oracle schema - different from
 their respective names.

 - user: "u_migrations"
 - user: "u_app"

 and both should use: "db_schema_xxx"

 It would be ok (actually preferred) to be just able to indicate the
 "schema_name" in the DB connection settings in

 This is currently not possible.

Ticket URL: <>
Django <>
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 [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit
For more options, visit