ดึงแถวด้วย query และ get

Every read from your database begins with the model's query attribute. It is your gateway to fetching rows as Python objects. 🔎

Call all() on a query to load every matching row into a plain Python list you can loop over.

Use first() when you want a single row. It returns the first match, or None if the table has nothing to give.

When you know the id, get() is the fastest path. Hand it the primary key and it returns that exact row.

If no row has that id, get() quietly returns None instead of raising. Always check before you use the result.

In a view, get_or_404() fetches by id and auto-aborts with a 404 page when the row is absent. No manual check needed.

Pair first_or_404() with a filter to grab one match or raise a clean 404 when nothing fits.

Need a tally, not the data? count() asks the database for the number directly, so you never pull full rows into memory.

Building a query does not touch the database yet. The SQL only runs when you call a method like all, first, or get.

Results come back as real model instances, so you read columns as ordinary attributes like user.name and user.email.

Use get for a known id, first for one of many, and all for the whole set. Choosing well keeps reads clear and fast.

You know a record's primary key. Which call fetches it most directly?

You now read data with query: all for lists, first for one, get by id, and the or_404 helpers for clean views. Nice work! 🎉