Introduction to how Django uses multiple database methods-JS Tutorial-php.cn

Introduction to how Django uses multiple database methods

巴扎黑

Release： 2017-09-07 10:17:08

Original

1578 people have browsed it

Some projects may involve the use of multiple databases, and the method is very simple. Next, this article will introduce you to the method of using multiple databases in Django. Friends who need it can refer to it

Some projects may involve the use of multiple databases. The method is very simple.

1. Set DATABASE in settings

For example, if you want to use two databases:

DATABASES = {
  &#39;default&#39;: {
    &#39;NAME&#39;: &#39;app_data&#39;,
    &#39;ENGINE&#39;: &#39;django.db.backends.postgresql&#39;,
    &#39;USER&#39;: &#39;postgres_user&#39;,
    &#39;PASSWORD&#39;: &#39;s3krit&#39;
  },
  &#39;users&#39;: {
    &#39;NAME&#39;: &#39;user_data&#39;,
    &#39;ENGINE&#39;: &#39;django.db.backends.mysql&#39;,
    &#39;USER&#39;: &#39;mysql_user&#39;,
    &#39;PASSWORD&#39;: &#39;priv4te&#39;
  }
}

Copy after login

This way Two databases have been identified, one with the alias default and the other with the alias user. The database alias can be determined arbitrarily.

The alias of default is special. When a Model is not specifically selected in the route, the default database is used by default.

Of course, default can also be set to empty:

DATABASES = {
  &#39;default&#39;: {},
  &#39;users&#39;: {
    &#39;NAME&#39;: &#39;user_data&#39;,
    &#39;ENGINE&#39;: &#39;django.db.backends.mysql&#39;,
    &#39;USER&#39;: &#39;mysql_user&#39;,
    &#39;PASSWORD&#39;: &#39;superS3cret&#39;
  },
  &#39;customers&#39;: {
    &#39;NAME&#39;: &#39;customer_data&#39;,
    &#39;ENGINE&#39;: &#39;django.db.backends.mysql&#39;,
    &#39;USER&#39;: &#39;mysql_cust&#39;,
    &#39;PASSWORD&#39;: &#39;veryPriv@ate&#39;
  }
}

Copy after login

In this way, because there is no default database, you need to set the default database for all Models, including the ones used. The Model in the third-party library performs database routing selection.

2. Specify app_label for the Model that needs to make database selection

class MyUser(models.Model):
  ...
  class Meta:
    app_label = &#39;users&#39;

Copy after login

3. Write Database Routers

Database Router is used to determine which database a Model uses. It mainly defines the following four methods:

db_for_read(model, **hints)

Specifies which database the model uses A database read.

db_for_write(model, **hints)

Specifies which database to use for model writing.

allow_relation(obj1, obj2, **hints)

Determine whether obj1 and obj2 can be related, mainly used for foreign key and many to many operations.

allow_migrate(db, app_label, model_name=None, **hints)

Determines whether the migrate operation can be run on the database with the alias db.

A complete example:

Database settings:

DATABASES = {
  &#39;default&#39;: {},
  &#39;auth_db&#39;: {
    &#39;NAME&#39;: &#39;auth_db&#39;,
    &#39;ENGINE&#39;: &#39;django.db.backends.mysql&#39;,
    &#39;USER&#39;: &#39;mysql_user&#39;,
    &#39;PASSWORD&#39;: &#39;swordfish&#39;,
  },
  &#39;primary&#39;: {
    &#39;NAME&#39;: &#39;primary&#39;,
    &#39;ENGINE&#39;: &#39;django.db.backends.mysql&#39;,
    &#39;USER&#39;: &#39;mysql_user&#39;,
    &#39;PASSWORD&#39;: &#39;spam&#39;,
  },
  &#39;replica1&#39;: {
    &#39;NAME&#39;: &#39;replica1&#39;,
    &#39;ENGINE&#39;: &#39;django.db.backends.mysql&#39;,
    &#39;USER&#39;: &#39;mysql_user&#39;,
    &#39;PASSWORD&#39;: &#39;eggs&#39;,
  },
  &#39;replica2&#39;: {
    &#39;NAME&#39;: &#39;replica2&#39;,
    &#39;ENGINE&#39;: &#39;django.db.backends.mysql&#39;,
    &#39;USER&#39;: &#39;mysql_user&#39;,
    &#39;PASSWORD&#39;: &#39;bacon&#39;,
  },
}

Copy after login

If you want to achieve the following effects:

The reading and writing of the Model whose app_label is auth are completed in auth_db, the rest of the Model writing is completed in the primary, and the reading is completed randomly in replica1 and replica2.

auth:

class AuthRouter(object):
  """
  A router to control all database operations on models in the
  auth application.
  """
  def db_for_read(self, model, **hints):
    """
    Attempts to read auth models go to auth_db.
    """
    if model._meta.app_label == &#39;auth&#39;:
      return &#39;auth_db&#39;
    return None
  def db_for_write(self, model, **hints):
    """
    Attempts to write auth models go to auth_db.
    """
    if model._meta.app_label == &#39;auth&#39;:
      return &#39;auth_db&#39;
    return None
  def allow_relation(self, obj1, obj2, **hints):
    """
    Allow relations if a model in the auth app is involved.
    """
    if obj1._meta.app_label == &#39;auth&#39; or \
      obj2._meta.app_label == &#39;auth&#39;:
      return True
    return None
  def allow_migrate(self, db, app_label, model_name=None, **hints):
    """
    Make sure the auth app only appears in the &#39;auth_db&#39;
    database.
    """
    if app_label == &#39;auth&#39;:
      return db == &#39;auth_db&#39;
    return None

Copy after login

In this way, the reading and writing of the Model whose app_label is auth are completed in auth_db, and associations are allowed. Migrate can only run in the auth_db database. .

The rest:

import random
class PrimaryReplicaRouter(object):
  def db_for_read(self, model, **hints):
    """
    Reads go to a randomly-chosen replica.
    """
    return random.choice([&#39;replica1&#39;, &#39;replica2&#39;])
  def db_for_write(self, model, **hints):
    """
    Writes always go to primary.
    """
    return &#39;primary&#39;
  def allow_relation(self, obj1, obj2, **hints):
    """
    Relations between objects are allowed if both objects are
    in the primary/replica pool.
    """
    db_list = (&#39;primary&#39;, &#39;replica1&#39;, &#39;replica2&#39;)
    if obj1._state.db in db_list and obj2._state.db in db_list:
      return True
    return None
  def allow_migrate(self, db, app_label, model_name=None, **hints):
    """
    All non-auth models end up in this pool.
    """
    return True

Copy after login

In this way, reading is done randomly in replica1 and replica2, and writing uses primary.

Finally set it in settings:

DATABASE_ROUTERS = [&#39;path.to.AuthRouter&#39;, &#39;path.to.PrimaryReplicaRouter&#39;]

Copy after login

When performing a migrate operation:

$ ./manage.py migrate
$ ./manage.py migrate --database=users

Copy after login

The migrate operation operates on the default database by default. To operate on other databases, you can use the --database option. What follows is the alias of the database.

Correspondingly, the dbshell, dumpdata, and loaddata commands all have the --database option.

You can also select the route manually:

Query:

>>> # This will run on the &#39;default&#39; database.
>>> Author.objects.all()
>>> # So will this.
>>> Author.objects.using(&#39;default&#39;).all() 
>>> # This will run on the &#39;other&#39; database.
>>> Author.objects.using(&#39;other&#39;).all()

Copy after login

Save:

>>> my_object.save(using=&#39;legacy_users&#39;)

Copy after login

Move:

>>> p = Person(name=&#39;Fred&#39;)
>>> p.save(using=&#39;first&#39;) # (statement 1)
>>> p.save(using=&#39;second&#39;) # (statement 2)

Copy after login

The above code will cause problems. When p is saved for the first time in the first database, a primary key will be generated by default, so use it When the second database is saved, p already has a primary key. This primary key will not cause problems if it is not used, but if it has been used previously, the original data will be overwritten.

There are two solutions;1. Clear the primary key before saving:

>>> p = Person(name=&#39;Fred&#39;)
>>> p.save(using=&#39;first&#39;)
>>> p.pk = None # Clear the primary key.
>>> p.save(using=&#39;second&#39;) # Write a completely new object.

Copy after login

2. Use force_insert

>>> p = Person(name=&#39;Fred&#39;)
>>> p.save(using=&#39;first&#39;)
>>> p.save(using=&#39;second&#39;, force_insert=True)

Copy after login

Delete:

Which database the object is obtained from and where to delete it

>>> u = User.objects.using(&#39;legacy_users&#39;).get(username=&#39;fred&#39;)
>>> u.delete() # will delete from the `legacy_users` database

Copy after login

If you want to transfer an object from the legacy_users database to the new_users database:

>>> user_obj.save(using=&#39;new_users&#39;)
>>> user_obj.delete(using=&#39;legacy_users&#39;)

Copy after login

The above is the detailed content of Introduction to how Django uses multiple database methods. For more information, please follow other related articles on the PHP Chinese website!