Skip to main content

Django select_related and prefetch_related

 


Difference between select_related and prefetch_related



Reducing SQL queries is one of the first steps when optimizing a Django project. There are two powerful methods included in the Django ORM to help us that can boost performance by creating a single more complex QuerySet rather than multiple, smaller queries.

In this project we will understand about  select_related and prefetch_related. 

Django use these two orm method to reduce sql queries in database based on different scenario. 


select_related

Lets assume  this two model we have. 

class Author(models.Model):
name = models.CharField(max_length=200)
def __str__(self):
return self.name


class Courses(models.Model):
name = models.CharField(max_length=200)
author = models.ForeignKey(Author,on_delete=models.CASCADE,related_name='courses')

def __str__(self):
return self.name


Here we have two mode. One is Author and another is Courses model. and we have added Author as foreign key in Courses mode. 

now suppose we want to get all the courses then we have to run this query

course = Courses.objects.all()

 Database query will be like this 

SELECT id, name,author_id FROM blog_courses

and now if we want to get the author it'll run a query again.example:

we have now Courses model objects in course variable. we want 0 index values author details.

courses[0].author

now it'll execute another query to get the author details.
Database query will be like this:

SELECT id, name, author_id FROM blog_courses

SELECT id, name FROM blog_author WHERE id = 1

This 2 query will execute if we want to get the author details from Courses mode.


But if we use select_related then we can reduce this expensive query execution in database

let's see what happen we use 

course = Courses.objects.select_related()

This query will also return all the objects from Courses model in course variable. In database it'll execute this sql query

SELECT id,name, author_id, FROM blog_courses INNER JOIN blog_author ON (author_id = id)


When we will use select_related() this will automatically INNER JOIN with Author model and get the all values from Author model. 

courses[0].author

Now if we can easily get the author value without executing another Query.


prefetch_related

Now let's deep drive into prefetch_related. In this scenario we want to get the Courses model objects from Author model. 
we'll query in Author model but we want data from Courses model. Author model has no connection with Courses model.

author = models.ForeignKey(Author,on_delete=models.CASCADE,related_name='courses')

Hope you can remember this field. we have used Author model as Foreign key in Courses model and we have used related_name

Using related_name and prefetch_related we can get Courses model data from Author model.

If we django query like this

author = Author.objects.prefetch_related()

Database Query:

SELECT id,name FROM blog_author ;


This will as same as Author.objects.all() query. 

But if we use

author = Author.objects.prefetch_related("courses")

In database it'll execute this sql query

SELECT id, name, author_id FROM blog_courses WHERE author_id IN (1, 2, 3, 4); 


See here it's executing a query in Courses model with where condition of Author id. Now we can get Courses Model object easily  in a single query. 



Comments

Popular posts from this blog

Implementing Advance Query Optimization in Django ORM

 Django's ORM makes database interactions seamless, allowing developers to write queries in Python without raw SQL. However, as applications scale, inefficient queries can slow down performance, leading to high latency and database load.  This guide explores advanced query optimization techniques in Django ORM to go beyond basic CRUD (Create, Read, Update, Delete) operations and improve efficiency.  1. Use QuerySet Caching to Avoid Repeated Queries Using cache reduces redundant queries for frequently accessed data. Caching helps reduce repeated database hits. 2. Avoid .count() on Large Datasets Using .count() on large tables can be expensive Inefficient way: Optimized way ( .exists() is Faster) 3. Use Indexes for Faster Lookups Indexes speed up queries on frequently filtered fields. Add db_index=True for frequently queried fields: 4. Optimize Bulk Inserts and Updated Performing operations on multiple records one by one is inefficient. Use bulk_create() for mass insert...

Database Indexing in Django application

  Database Indexing Database indexing is a technique used to optimize the performance of database queries by allowing the database management system (DBMS) to quickly locate and retrieve specific rows of data. Indexes are data structures that provide a faster way to look up records based on the values stored in one or more columns of a table. When you create an index on a table, the DBMS creates a separate data structure that maps the values in the indexed columns to the corresponding rows in the table. Default Type of Index is B-Tree Index ( The king of all indexes) বইতে কোন টপিক খুজতে গেলে আমরা টেবিল অফ কনটেন্ট থেকে দেখি এই টপিক কত নম্বর পেজে আছে।যাতে করে আমাদের পুরো বই খুজতে না হয়। ডেটাবেজ ইনডেক্সিং ও তেমনই একটা ইফিসিয়েন্ট টেকনিক।ডেটাবেজে কোন ডেটাকে দ্রুত খুজে বের করার জন্য ইনডেক্সিং করা লাগে।যদি এমন হয় একটা কুয়েরি বার বার এক্সিকিউট করতে হচ্ছে এবং একটা কলাম থেকে ভ্যালু বার বার খুজতে হচ্ছে তখন আমরা সেই কলামে ইনডেক্সিং করতে পারি।এর মাধ্যমে কোন ডেটা দ্রুত রিট্রাইভ করা যায়।কিন্তু ই...