N020-M4 Tier 2 · Core SQL · medium ecommerce · Brightlane

Return each premium product paired with every category, returning the product name, price, and category name

Part of CROSS JOIN in SQL

The problem

Brightlane's pricing team wants to analyse how premium products — those with a list price above $500 — could be positioned across every available category.

Write a query to return each premium product paired with every category, returning the product name, price, and category name.

Assumptions:

  • The products table contains every product in the catalogue.
  • The categories table contains every defined category.
  • The premium condition narrows the result to products with price > 500 before they are paired with categories.

Output:

  • One row per premium-product × category combination, with columns product_name, price, and category_name.
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

Run previews · Check grades

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

Worked solution Try it yourself first
Solution query
SELECT
  p.name AS product_name,
  p.price,
  c.name AS category_name
FROM
  products p
  CROSS JOIN categories c
WHERE
  p.price > 500

The shape

WHERE p.price > 500 narrows products to the premium cohort, and CROSS JOIN categories c expands each premium product across every category — including the category it currently sits in. The output carries three columns: the product name, its price (for the pricing team to see directly), and the candidate category.

Clause by clause

  • FROM products p CROSS JOIN categories c is the unconditional pairing. Every row in products combines with every row in categories.
  • WHERE p.price > 500 filters the left side to products whose list price exceeds $500. The comparison is strict — a product at exactly 500 does not pass. Premium, by the pricing team's working definition, sits above that threshold.
  • p.name AS product_name and p.price read two columns from the products side. The price column doesn't need an alias because it's already named appropriately; PostgreSQL will return it as price.
  • c.name AS category_name reads the candidate category from the right side. The alias c disambiguates this name column from the product's name column on the left.

Why include price in the output

The team is analysing positioning. Seeing each pairing alongside its price keeps the analysis self-contained — the reader doesn't have to cross-reference back to the product table to know which premium tier a given pairing represents. A $1,199 product positioned in Home Goods reads differently from a $549 product positioned in the same category. Carrying the price through makes that visible in the result without a second query.

You practiced CROSS JOIN against a price-filtered cohort. The premium-positioning use case is the everyday version of "hypothetical placement," where the cross-product is the answer because no actual relationship has been decided yet.

How you actually get good at SQL

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

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.