Django ORM Mastery: QuerySets, Filtering, Slicing & Lazy Evaluation

Q: What does it mean that Django QuerySets are 'lazy'?

Lazy evaluation means creating a QuerySet does not touch the database. Django only converts the QuerySet into an actual SQL query and hits the database when you evaluate it (e.g. iterating over it in a loop, slicing it with a step, calling `len()`, `list()`, or `bool()`).

Q: What is the difference between get() and filter()?

`filter()` always returns a `QuerySet` (a list-like collection of 0, 1, or many objects). `get()` returns exactly one model instance; it raises `DoesNotExist` if no matching record is found, and `MultipleObjectsReturned` if more than one record matches.

Q: How does case-insensitive search work in Django field lookups?

Use the `__icontains`, `__iexact`, `__istartswith`, or `__iendswith` lookups. The leading 'i' instructs the database engine to perform case-insensitive comparison (translating to `ILIKE` in PostgreSQL or `LOWER(field) LIKE LOWER(...)` in standard SQL).

Q: Can I use Python negative slicing on Django QuerySets?

No. Negative slicing like `BlogPost.objects.all()[-5:]` raises `AssertionError: Negative indexing is not supported`. To get the last 5 records, reverse the order first: `BlogPost.objects.order_by('-id')[:5]`.

Django's Object-Relational Mapper (ORM) allows developers to interact with database records entirely using Python syntax instead of writing raw SQL. Understanding how QuerySets are constructed, filtered, and evaluated is fundamental to building high-performance web applications.

Essential Field Lookup Operators

Lookup Operator	Django Python Syntax	SQL Translation
`exact` / `iexact`	`Post.objects.filter(slug__iexact='django-orm')`	`WHERE UPPER(slug) = UPPER('django-orm')`
`contains` / `icontains`	`Post.objects.filter(title__icontains='tutorial')`	`WHERE title ILIKE '%tutorial%'`
`gt` / `gte`	`Post.objects.filter(reading_time__gte=10)`	`WHERE reading_time >= 10`
`lt` / `lte`	`Post.objects.filter(price__lt=50.00)`	`WHERE price < 50.00`
`in`	`Post.objects.filter(id__in=[1, 4, 9])`	`WHERE id IN (1, 4, 9)`
`range`	`Post.objects.filter(created_at__range=(start, end))`	`WHERE created_at BETWEEN start AND end`
`isnull`	`Post.objects.filter(published_at__isnull=True)`	`WHERE published_at IS NULL`

Chaining QuerySets and Lazy Evaluation

QuerySets are chainable — applying a filter returns a new QuerySet, allowing you to combine criteria dynamically without firing multiple queries:

# None of these statements hit the database yet! (Lazy evaluation)
posts = BlogPost.objects.filter(is_published=True)
posts = posts.filter(category__name='Technology')
posts = posts.exclude(author__user__username='spammer')
posts = posts.order_by('-created_at')[:10]  # LIMIT 10

# Database is hit RIGHT HERE when we iterate over the queryset:
for post in posts:
    print(post.title)

BCA Viva Question: When is a QuerySet Evaluated?

A QuerySet is evaluated when: 1) It is iterated over (for obj in qs:), 2) It is sliced with a step (qs[::2]), 3) Sized with len(qs) or converted with list(qs), or 4) Evaluated in a boolean test (if qs:).

Frequently Asked Questions (FAQ) - Student & Interview Review

Q1. What does it mean that Django QuerySets are 'lazy'?

Lazy evaluation means creating a QuerySet does not touch the database. Django only converts the QuerySet into an actual SQL query and hits the database when you evaluate it (e.g. iterating over it in a loop, slicing it with a step, calling `len()`, `list()`, or `bool()`).

Q2. What is the difference between get() and filter()?

`filter()` always returns a `QuerySet` (a list-like collection of 0, 1, or many objects). `get()` returns exactly one model instance; it raises `DoesNotExist` if no matching record is found, and `MultipleObjectsReturned` if more than one record matches.

Q3. How does case-insensitive search work in Django field lookups?

Use the `__icontains`, `__iexact`, `__istartswith`, or `__iendswith` lookups. The leading 'i' instructs the database engine to perform case-insensitive comparison (translating to `ILIKE` in PostgreSQL or `LOWER(field) LIKE LOWER(...)` in standard SQL).

Q4. Can I use Python negative slicing on Django QuerySets?

No. Negative slicing like `BlogPost.objects.all()[-5:]` raises `AssertionError: Negative indexing is not supported`. To get the last 5 records, reverse the order first: `BlogPost.objects.order_by('-id')[:5]`.