นำเข้าและตรวจสอบโมเดล

Before you can query data, you import the model class into the shell. Pull it from the app where you defined it.

The import path is always appname.models. So a Post in the blog app lives at blog.models, matching your folder layout.

Type the class name alone to see Django confirm the model. It echoes the class so you know the import worked.

Each model carries a manager called objects. It is your gateway to every query, like fetching or counting rows.

To list a model's columns, read its hidden _meta object. It exposes the fields Django mapped to your table.

A quick comprehension turns that into a clean list of field names, handy when you forget a column.

You can grab a single field by name with get_field. It returns the field object so you can read its details.

Ask a field for its type with type(). This tells you whether a column is a CharField, IntegerField, and so on.

Plain Python tools still work. Run help on the model to read its docstring and see available attributes.

Need several models? Import them together on one line so you can cross-reference data without retyping.

Inspecting first saves time. Knowing the exact field names prevents typos when you start filtering real records.

How do you list the fields a model defines?

You imported models with appname.models, met the objects manager, and used _meta to inspect fields before querying. 🔍