All Products with Prices — FROM Clause in SQL

The problem

Brightlane's merchandising team is building a master price list ahead of the Q4 catalog refresh.

Write a query to return every product's ID, name, and price.

Assumptions:

The products table contains every item in Brightlane's catalog.
Each product has an id, a name, and a price recorded.

Output:

One row per product, with columns id, name, and price.

Schema · ecommerce 5 tables

categories

id integer

name text

parent_id? integer

products

id integer

name text

category_id integer

price numeric

stock_qty integer

attributes? jsonb

order_items

id integer

order_id integer

product_id integer

quantity integer

unit_price numeric

customers

id integer

name text

email text

city? text

country text

created_at timestamptz

is_active boolean

orders

id integer

customer_id integer

ordered_at timestamptz

status text

total_amount numeric

Check answerShift Ctrl ↵

Run previews · Check grades

Write a query, then run it to see results here.

Worked solution Try it yourself first

Solution query

SELECT
  id,
  name,
  price
FROM
  products

The shape

FROM products points the query at the catalog table, and the three named columns in the SELECT list shape every row into the exact slice the merchandising team needs.

Clause by clause

SELECT id, name, price names the three columns to return, in that order. The master price list lands with id on the left, name in the middle, and price on the right — exactly the column layout the prompt asks for.
FROM products is the row source. PostgreSQL reads every row from the products table and hands the full population to the SELECT list. With no WHERE, every row in the catalog survives — Apex Titan 15 at $999, Vega S24 Ultra at $899, and on through the full inventory.

Why this and not `SELECT *`

SELECT * would also return the catalog, but with every column the products table happens to carry — category IDs, stock levels, anything else the schema includes. The refresh only needs three. Naming them keeps the result stable: if a new column gets added to products next quarter, this query still returns the same three. A SELECT * query would silently start returning the new column too, which is the kind of drift that breaks downstream consumers.

You practiced reading rows from a single table by naming it in FROM and listing the columns you want in SELECT. The SELECT … FROM skeleton is the foundation for every query you'll write in SQL.

Return every product's ID, name, and price

The shape

Clause by clause

Why this and not `SELECT *`

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

The shape

Clause by clause

Why this and not SELECT *

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

Why this and not `SELECT *`