Products Priced Over 100 — WHERE Clause in SQL

The problem

Brightlane's buying team is reviewing the premium product range ahead of a catalog presentation.

Write a query to return the name and price of every product priced above $100.

Assumptions:

The products table contains every item in Brightlane's catalog.
The price column records each product's selling price in dollars.

Output:

One row per qualifying product, with columns 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
  name,
  price
FROM
  products
WHERE
  price > 100

The shape

A single numeric comparison on price does the filtering — the catalog walks past row by row, and only rows whose price clears the $100 threshold come through.

Clause by clause

SELECT name, price returns the two columns the buying team is reviewing: what the product is called and what it costs. Order matches the prompt's required output.
FROM products is the catalog source — every item Brightlane sells, premium or not.
WHERE price > 100 keeps only rows whose price is strictly greater than 100. The literal 100 has no quotes because it's a number; PostgreSQL compares it numerically against the price column. A product priced at exactly 100 would not survive — > is strict.

Why this and not `>=`

The prompt says "priced above $100," which excludes the boundary itself. Strict > matches that wording. If the prompt had said "priced at or above $100" or "$100 and up," >= would be the right operator and a $100 item would qualify. The two operators differ by exactly one value: the boundary. Picking the wrong one shifts the row count by however many rows sit exactly at the threshold.

You practiced filtering rows with a numeric comparison (price > 100). Threshold filters on numeric columns recur in every report that segments by amount.

Return the name and price of every product priced above $100

The shape

Clause by clause

Why this and not `>=`

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 >=

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

Why this and not `>=`