N008-M4 Tier 1 · Foundations · medium ecommerce · Brightlane

Return the ID and name of every product after the first 5

Part of LIMIT and OFFSET in SQL

The problem

Brightlane's inventory team is processing the product catalogue alphabetically and has already handled the first 5 products. They want a list of every remaining product so they can continue from where they left off.

Write a query to return the ID and name of every product after the first 5.

Assumptions:

  • The products table contains every product in Brightlane's catalogue.
  • OFFSET without a LIMIT is valid — PostgreSQL skips the specified number of rows and returns every row after that.

Output:

  • One row per remaining product, with columns id and name, sorted by name ascending.
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
  id,
  name
FROM
  products
ORDER BY
  name
OFFSET
  5

The shape

OFFSET 5 without a paired LIMIT skips the first five alphabetical products and returns every row after — the rest of the catalogue from row 6 onward.

Clause by clause

  • SELECT id, name picks the two columns the inventory team needs to continue their walk through the catalogue.
  • FROM products reads the full catalogue.
  • ORDER BY name sorts alphabetically — the same order the team has been processing the catalogue in. Without the same sort, "the first 5 we already handled" and "the rows we skip" wouldn't line up.
  • OFFSET 5 discards the first five rows of the sorted result. Coffee Table at id 25 lands as the first row returned because it sits at position 6 in the alphabetical sort.

Why no LIMIT

LIMIT and OFFSET are independent controls. LIMIT caps the back of the result; OFFSET trims the front. Either can appear without the other. Here the team wants everything past the first five rows, with no cap on how many products come back — so OFFSET appears alone. PostgreSQL skips the first five rows and then keeps returning rows until the result set is exhausted, which leaves 58 products in this catalogue.

The two clauses can also appear in the other arrangement. LIMIT 5 alone returns just the first five products — the rows the team has already handled. Together, LIMIT 5 OFFSET 5 would return rows 6 through 10 as a single page. The same two controls compose into top-N, bottom-N, paginated windows, and tail-of-the-list queries depending on which is present and how they're sized.

You practiced using OFFSET without a LIMIT to return everything past a starting point. The two clauses are independent controls — OFFSET alone trims the front of the result, LIMIT alone trims the back, together they carve out a window.

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.