select_related pour les clés étrangères

select_related tells Django to fetch related rows up front in the same query, so loops stop firing extra trips. ⚡

Under the hood it adds a SQL JOIN, pulling the parent and its related row together in one efficient round trip.

Pass the related field name to select_related on your queryset, and the join happens automatically when the data loads.

Now looping over those books and reading each author runs a single query instead of one hundred and one. Same code, huge win.

Use it for ForeignKey and OneToOne fields, where each object points to exactly one related row that a join can grab.

It does not work for many-to-many or reverse one-to-many links, because a join cannot fold many rows into one cleanly.

You can span multiple hops with double underscores, joining across more than one foreign key in a single query.

Pass several field names to grab multiple relations together, all stitched into the same optimized query.

The query still waits until you actually use the data, so chaining filters and order_by before it stays cheap and flexible.

Joins add columns, so do not over-select. Grab only the relations you truly read to keep each row lean.

See a foreign key accessed in a loop? Reach for select_related first. It becomes second nature fast. 🎯

select_related joins ForeignKey and OneToOne data in one query, killing N+1 for single-row links. Chain hops with double underscores. ✅