Databases
StackOverflow2013
Postsdbo
PODjango multi-database routing
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango multi-database routing
    primarykey
    data
    text
    <p>I have been using manual db selection to cope with a project which has two seperate dbs. I have defined my databases in the settings. After some further reading it seems that database routing is actually the way to go with this. However, after reading the docs and some relevant posts here I am more confused than ever.</p> <p>In my settings I have:</p> <pre><code>DATABASES = { 'default': { .... }, 'my_db2': { .... } } DATABASE_ROUTERS = ['myapp2.models.MyDB2Router',] </code></pre> <p>I know I have to define my router class (I <strong>think</strong> in myapp2.models.py) like so:</p> <pre><code>class MyDB2Router(object): """A router to control all database operations on models in the myapp2 application""" def db_for_read(self, model, **hints): if model._meta.app_label == 'myapp2': return 'my_db2' return None def db_for_write(self, model, **hints): if model._meta.app_label == 'myapp2': return 'my_db2' return None def allow_relation(self, obj1, obj2, **hints): if obj1._meta.app_label == 'myapp2' or obj2._meta.app_label == 'myapp2': return True return None def allow_syncdb(self, db, model): if db == 'my_db2': return model._meta.app_label == 'myapp2' elif model._meta.app_label == 'myapp2': return False return None </code></pre> <p>Then what? Does each model require a meta.app_label or is that automatic? Aside from that, I still get an error: </p> <p>django.core.exceptions.ImproperlyConfigured: Error importing database router JournalRouter: "cannot import name connection</p> <p>Can anyone help me understand what is happening and what is going wrong? Any help much appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSerjik
    1. USDarwin Tech
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango multi-database routing
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODjango multi-database routing
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODjango multi-database routing
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOK, so I just solved my own problem. The router class goes into a separate file called routers.py under /myapp2. No meta.app_label is required as I guess it is automatically assigned. Hope this helps someone.
      singulars
      1. PODjango multi-database routing
      1. USDarwin Tech
    2. COCreate a new answer to your question and accept it then.
      singulars
      1. PODjango multi-database routing
      1. USIvan Kharlamov
    3. COYou only need to use the [`app_label`](https://docs.djangoproject.com/en/dev/ref/models/options/#app-label) option if the model is defined outside of the `models.py`, otherwise it is assigned automatically.
      singulars
      1. PODjango multi-database routing
      1. USAlasdair
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload