UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database routers if any are installed. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database. You don’t have to do anything to activate the default routing scheme – it is provided

UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database routers if any are installed. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database. You don’t have to do anything to activate the default routing scheme – it is provided

UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database routers if any are installed. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database. You don’t have to do anything to activate the default routing scheme – it is provided

UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database routers if any are installed. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database. You don’t have to do anything to activate the default routing scheme – it is provided

UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database routers if any are installed. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database. You don’t have to do anything to activate the default routing scheme – it is provided

UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database control the database used. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database. You don’t have to do anything to activate the default routing scheme – it is provided

UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database control the database used. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database. You don’t have to do anything to activate the default routing scheme – it is provided

UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database routers if any are installed. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database. You don’t have to do anything to activate the default routing scheme – it is provided

UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database routers if any are installed. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database. You don’t have to do anything to activate the default routing scheme – it is provided

UPDATE, INSERT, or DELETE queries. In these cases, you can always access the database directly, routing around the model layer entirely. The object django.db.connection represents the default database routers were added in 1.10.1. Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain ‘sticky’ to (i.e., an object retrieved from the foo database will be saved on the same database). The default routing scheme ensures that if a database isn’t specified, all queries fall back to the default database