Django Slugs and UUIDs

Why We have to Use UUID or SlugFlied:

The django default id or primary_key( pk ) is currently auto-incrementing id. Among other concerns, it tells a potential hacker exactly how many records you have in your database; it tells them exactly what the id is which can be used in a potential attack; and there can be synchronization issues if you have multiple front-ends.

There are two alternative approaches. UUID and SlugFiled

UUIDField:

A field for storing universally unique identifiers. Uses Python’s UUID class. When used on PostgreSQL and MariaDB 10.7+, this stores in a uuid datatype, otherwise in a char(32).

Example Code:

class UserProfile(models.Model):
    id = models.UUIDField(primary_key=True,default=uuid.uuid4,editable=False)
    name = models.CharField(max_length=500)
    email = models.EmailField()
    
    def __str__(self):
        return self.name
    
    def get_absolute_url(self):
        return reverse("user_details", args=[str(self.id)])

SlugField:

Slug is a newspaper term. A slug is a short label for something, containing only letters, numbers, underscores or hyphens. They’re generally used in URLs. Like a CharField, you can specify max_length. If max_length is not specified, Django will use a default length of 50.

Example Code:

class Post(models.Model):
    slug = models.CharField(max_length=250)

For example, in our example of “Django for Professionals” its slug could be django-for-professionals. There’s even a SlugField model field that can be used and either added when creating the title field by hand or auto-populated upon save.

The main challenge with slugs is handling duplicates though this can be solved by adding random strings or numbers to a given slug field. The synchronization issue remains though. A better approach is to use a UUID (Universally Unique IDentifier) which Django now supports via a dedicated UUIDField

Comments

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...

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. ...

Python Closure

Imagine you have a function called outer_function that defines another function called inner_function inside it. Now, inner_function can access variables from the outer_function . When inner_function is returned from outer_function , it still remembers those variables even though outer_function has finished executing. This is the essence of a closure in Python. Example Code: In this example, outer_function takes a parameter x and defines inner_function inside it. inner_function can access x from the outer_function . When outer_function(10) is called, it returns inner_function , effectively creating a closure. Now, closure_example holds a reference to inner_function along with the value x (which is 10 in this case). When closure_example(5) is called, it adds 5 to the value of x (which is 10), resulting in 15. So, a closure "closes over" the environment in which it was defined, allowing it to access variables from its enclosing scope even after that scope has fi...

Django Interview Preparation

Search This Blog