Database generated columns are a powerful feature, introduced in Django 5.0 with GeneratedField. A GeneratedField is computed directly by the database from other fields in the same row, so values stay consistent without triggers or extra Python code.

This talk explains GeneratedField by example, focusing on practical patterns you can use in real Django projects. Instead of a feature tour, each example answers a simple question: why use a GeneratedField here, and what are the trade-offs?

We start with small and readable cases, such as simple calculations and status fields, then move to more realistic scenarios: full names, values derived from JSON fields, and database features like full-text search vectors. Each example shows how Django expressions translate to SQL and what the database actually computes.

Since Django 5.0, GeneratedField has improved quickly. Some early limitations are no longer relevant, and the examples reflect current supported versions, including Django 5.2 LTS and Django 6.0. The talk also covers common pitfalls: stored vs virtual columns, immutability rules, backend differences, and when values need to be refreshed after saving.

You will leave with concrete recipes, a clearer mental model, and simple guidelines to decide when GeneratedField is a good choice and when other solutions are better.