values, values_list와 count

Full model objects carry every field. When you only need a column or two, lighter tools fetch less data and run faster.

Call values() and each row comes back as a dictionary instead of a model instance. Handy for JSON and quick reads.

Name the fields you pass to values() and Django selects just those columns, keeping each dictionary small and focused.

Prefer tuples? values_list() gives each row as a tuple of values in the order you named the fields.

Asking for one field? Add flat=True to get a clean list of plain values instead of one-item tuples.

Remember, flat=True only works with a single field. Pass two fields and Django raises an error to keep things clear.

Both values() and values_list() stay lazy QuerySets, so you can filter and order them before they ever run.

Need just a total? count() asks the database to count rows directly, far cheaper than pulling them all into Python.

Use count() when you only need the number. Calling len() first loads every object, then counts in memory.

To check if rows exist, exists() beats count(). It stops at the first match and returns a simple True or False.

Mix these freely: filter to narrow, then values_list for a tidy list or count for a total. Each query stays lean.

You want a plain list of every book title, not tuples or dictionaries. What do you use?

Wonderful! values() gives dicts, values_list() gives tuples, and count() totals rows in the database. 📊