Python Tutorial
Django Field Lookups
Field lookups are the SQL WHERE clause: startswith, contains, lt, gt, year, and more. Write them as field__lookup=value.
Common Lookups
Double underscore separates the field from the lookup.
Member.objects.filter(firstname__startswith="E")
Member.objects.filter(lastname__contains="Ref")
Member.objects.filter(id__gt=2)
Member.objects.filter(joined_date__year=2022)📘 Real-World Deep Dive
Knowing <strong>Django Lookups (Django)</strong> well is what turns Django from a curiosity into a daily tool — you'll reach for it in nearly every real project.
Real-Life Scenario
An end-to-end usage of Django Lookups that you'd actually see in a data pipeline or analytics notebook.
Real-Life Example
Book.objects.filter(author__name__icontains="lovelace")
Book.objects.filter(pub__year__lt=2000)
Book.objects.filter(tags__name__in=["django", "python"])Expected Output
(no output)Common mistakes
- Forgetting to call
.save()on a model instance after mutation silently persists nothing. - Reading every row with
Model.objects.all()on a 1 M-row table OOMs the worker — use.iterator()for streaming. - Queries inside loops produce N+1 problems — pull related rows with
select_related/prefetch_related. - Treating Django Lookups as a black box without reading the docs — the API has subtle defaults that bite when you scale.
🚀 Performance & Best Practices
- Add database indexes (
db_index=TrueorMeta.indexes) on columns used infilter. - Use
cache_pageon read-heavy views and setCONN_MAX_AGEto keep DB connections warm. - Generate migrations with
python manage.py makemigrations --dry-run --verbosity 3and review before committing. - When working with Django, prefer vectorised / batched operations over Python loops.
🧪 Try It Yourself
- Reproduce the snippet on a representative slice of your own data.
- Profile the snippet with
cProfileortimeitand find the single biggest improvement. - Generalise the snippet into a small, reusable function you can drop into future projects.