Table of contents
Differences between select_related and prefetch_related in Django
Differences between select_related and prefetch_related in Django
The select_related and _prefetch_relate_d methods are used to reduce the number of queries made to the database. This translates into response time for each view. In addition, using these methods is one of the actions to implement to improve the performance of a Django application
select_related
The select_related method is used to follow a relationship of type ForeignKey or OneToOneField to the respective objects it points to and obtain them..
When using select_related we will have a longer query, however, the advantage is that it will no longer be necessary to access the database again to obtain the objects of the related model.
Simplified diagram of how select_related works
Consider this example:
from django.db import models
class Principal(models.Model):
name = models.CharField(max_length=256)
class Derivado(models.Model):
name = models.CharField(max_length=256)
principal = models.ForeignKey(
"Principal", related_name="derivados", on_delete=models.CASCADE
)
If we try to access the object pointed to by the Foreign Key relationship, a new database query will be generated. select_related avoids that extra query for each object.
{% for object in queryset %}
<p>{{object.name}}</p>
<small>{{object.principal.name}}</small>
{% endfor %}
For example, if we have three Derived objects related to a single main object:
- A main query that retrieves all objects Derivative
- Three queries, exactly the same, one for each time we access the main object from the Derived object.
Use in a query
To use select_related we call it from our query, passing it the name of the field that corresponds to our relationship with the other model.
Derivado.objects.select_related("principal")
Internal operation of select_related
How select_related works internally, select_related replaces multiple queries being performed by a single INNER JOIN at the database level:
SELECT "my_app_derivado"."id",
"my_app_derivado"."name",
"my_app_derivado"."principal_id"
FROM "my_app_derivado"
SELECT "my_app_principal"."id",
"my_app_principal"."name"
FROM "my_app_principal"
WHERE "my_app_principal"."id" = '1'
SELECT "my_app_principal"."id",
"my_app_principal"."name"
FROM "my_app_principal"
WHERE "my_app_principal"."id" = '1'
SELECT "my_app_principal"."id",
"my_app_principal"."name"
FROM "my_app_principal"
WHERE "my_app_principal"."id" = '1'
This reduces multiple SQL queries to a single, longer query.
SELECT "my_app_derivado"."id",
"my_app_derivado"."name",
"my_app_derivado"."principal_id",
"my_app_principal"."id",
"my_app_principal"."name"
FROM "my_app_derivado"
INNER JOIN "my_app_principal"
ON ("my_app_derivado"."principal_id" = "my_app_principal"."id")
prefetch_related
If the select_related method retrieves a single object from a single relationship field, the prefetch_related method is used when we have a multiple relationship with another model, i.e. a relationship of type **ManyToMany or a reverse ForeignKey.
Simplified diagram of how prefetch_related works
Consider this example, note the ManyToManyField field towards the Principal model.
from django.db import models
class Principal(models.Model):
name = models.CharField(max_length=256)
class MultiplesPrincipales(models.Model):
name = models.CharField(max_length=256)
principales = models.ManyToManyField("Principal", related_name="multiples")
If we access the field that represents the multiple relation of our object, without using prefetch_related, we will be impacting the database with a new query.
{% for object in queryset %}
<p>{{object.name}}</p>
{% for principal in object.principales.all %}
<!-- Una nueva consulta cada vez -->
<p><small>{{principal.name}}</small></p>
{% endfor %}
{% endfor %}
Use in a query
To use the prefetch_related method call it at the end of our query, choosing the field that represents the many-to-many relationship in our object.
queryset = MultiplesPrincipales.objects.prefetch_related("principales")
Inner workings of prefetch_related
How does prefecth_related work internally? The prefetch_related method replaces the multiple SQL queries by only 2 SQL queries: one for the main query and the other for the related objects, then it will join the data using Python.
SELECT "my_app_principal"."id",
"my_app_principal"."name"
FROM "my_app_principal"
INNER JOIN "my_app_multiplesprincipales_principales"
ON ("my_app_principal"."id" = "my_app_multiplesprincipales_principales"."principal_id")
WHERE "my_app_multiplesprincipales_principales"."multiplesprincipales_id" = '1'
SELECT "my_app_principal"."id",
"my_app_principal"."name"
FROM "my_app_principal"
INNER JOIN "my_app_multiplesprincipales_principales"
ON ("my_app_principal"."id" = "my_app_multiplesprincipales_principales"."principal_id")
WHERE "my_app_multiplesprincipales_principales"."multiplesprincipales_id" = '2'
SELECT "my_app_principal"."id",
"my_app_principal"."name"
FROM "my_app_principal"
INNER JOIN "my_app_multiplesprincipales_principales"
ON ("my_app_principal"."id" = "my_app_multiplesprincipales_principales"."principal_id")
WHERE "my_app_multiplesprincipales_principales"."multiplesprincipales_id" = '3'
SELECT "my_app_principal"."id",
"my_app_principal"."name"
FROM "my_app_principal"
INNER JOIN "my_app_multiplesprincipales_principales"
ON ("my_app_principal"."id" = "my_app_multiplesprincipales_principales"."principal_id")
WHERE "my_app_multiplesprincipales_principales"."multiplesprincipales_id" = '4'
The multiple queries above are reduced to only 2 SQL queries.
SELECT "my_app_multiplesprincipales"."id",
"my_app_multiplesprincipales"."name"
FROM "my_app_multiplesprincipales"
SELECT ("my_app_multiplesprincipales_principales"."multiplesprincipales_id") AS "_prefetch_related_val_multiplesprincipales_id",
"my_app_principal"."id",
"my_app_principal"."name"
FROM "my_app_principal"
INNER JOIN "my_app_multiplesprincipales_principales"
ON ("my_app_principal"."id" = "my_app_multiplesprincipales_principales"."principal_id")
WHERE "my_app_multiplesprincipales_principales"."multiplesprincipales_id" IN ('1', '2', '3', '4')
