1. Lighthouse

Level 1 · Price list, most expensive first

The request

From Jessica Turner, Merchandising Manager

“Thanks for the price sheet. Could you sort it so the most expensive products are at the top? If two products cost the same, list them alphabetically.”

Your goal

From products, return name and unit_price, sorted by unit_price from highest to lowest, then by name from A to Z when prices tie.

  • Read from the products tablenot done yet
  • Show exactly name unit_pricenot done yet
  • 120 rows, sorted as askednot done yet

Your query

SQL

Loading the editor…

    ResultPreview of products · press Run to see yours
    Preview of products
    product_idnamecategorysubcategoryunit_price
    101Vale Velvet LoveseatFurnitureSofas1659.00
    102Alder Oak Coffee TableFurnitureTables919.00
    103Orchard Rattan Dining ChairFurnitureChairs789.00
    104Upland Oak BookcaseFurnitureStorage429.00

    Mote checks your result

    Press Run. Each row that matches the goal becomes a firefly in your lantern.

    Tables

    Harbor & Pine store data, ready to query.

    products120 rows · 8 columns
    • product_idinteger
    • namevarchar
    • categoryvarchar
    • subcategoryvarchar
    • unit_pricedecimal
    • unit_costdecimal
    • launched_ondate
    • is_activeboolean
    First 5 rows of products
    product_idnamecategorysubcategoryunit_priceunit_costlaunched_onis_active
    101Vale Velvet LoveseatFurnitureSofas1659.00NULL2023-09-11true
    102Alder Oak Coffee TableFurnitureTables919.00503.502024-05-16true
    103Orchard Rattan Dining ChairFurnitureChairs789.00429.872023-05-27true
    104Upland Oak BookcaseFurnitureStorage429.00214.702022-12-20true
    105Avery Leather Bed FrameFurnitureBeds449.00232.702021-08-31true
    customers2,018 rows · 9 columns
    • customer_idinteger
    • first_namevarchar
    • last_namevarchar
    • emailvarchar
    • cityvarchar
    • statevarchar
    • signup_datedate
    • segmentvarchar
    • referral_sourcevarchar
    First 5 rows of customers
    customer_idfirst_namelast_nameemailcitystatesignup_datesegmentreferral_source
    1OwenHudsonowen.hudson@icloud.comSan FranciscoCA2022-06-02consumersearch
    2DouglasMendozadmendoza69@gmail.comAtlantaGA2022-06-02consumerNULL
    3HenryBrookshbrooks@lakesidecafe.comLos AngelesCA2022-06-04businessNULL
    4BrianGrahambgraham@bluecedarhomes.comSeattleWA2022-06-06businesspinterest
    5KyleJimenezkjimenez27@yahoo.comIndianapolisIN2022-06-07consumerNULL
    orders12,000 rows · 7 columns
    • order_idinteger
    • customer_idinteger
    • order_datetimestamp
    • statusvarchar
    • channelvarchar
    • shipping_feedecimal
    • coupon_codevarchar
    First 5 rows of orders
    order_idcustomer_idorder_datestatuschannelshipping_feecoupon_code
    10011252023-01-01 20:51:19completedweb0.00NULL
    10021562023-01-02 07:58:46completedweb0.00NULL
    1003222023-01-02 10:25:27completedmarketplace4.99WELCOME10
    1004482023-01-02 11:21:51completedmarketplace4.99WELCOME10
    1005822023-01-02 11:43:36completedweb0.00WELCOME10
    order_items30,338 rows · 6 columns
    • order_item_idinteger
    • order_idinteger
    • product_idinteger
    • quantityinteger
    • unit_pricedecimal
    • discount_pctdecimal
    First 5 rows of order_items
    order_item_idorder_idproduct_idquantityunit_pricediscount_pct
    11001121931.990.00
    21001154311.990.00
    31002154411.990.00
    410021941149.000.00
    51002193219.990.00
    returns1,673 rows · 5 columns
    • return_idinteger
    • order_item_idinteger
    • returned_ondate
    • reasonvarchar
    • refund_amountdecimal
    First 5 rows of returns
    return_idorder_item_idreturned_onreasonrefund_amount
    1142023-01-10damaged83.69
    2422023-01-10wrong_item19.99
    31052023-01-14wrong_item10.99
    4242023-01-16changed_mind26.99
    51262023-01-16late20.99
    employees60 rows · 8 columns
    • employee_idinteger
    • first_namevarchar
    • last_namevarchar
    • departmentvarchar
    • titlevarchar
    • manager_idinteger
    • hire_datedate
    • salaryinteger
    First 5 rows of employees
    employee_idfirst_namelast_namedepartmenttitlemanager_idhire_datesalary
    1CatherineHaleExecutiveChief Executive OfficerNULL2016-03-01285000
    2RobertKimExecutiveChief Operating Officer12017-01-09235000
    3MeganCollinsSalesHead of Sales12018-04-16172000
    4ChloeGutierrezSalesAccount Executive32020-01-2172000
    5FrankBellSalesAccount Executive32023-05-2173000
    web_sessions40,000 rows · 7 columns
    • session_idinteger
    • customer_idinteger
    • started_attimestamp
    • devicevarchar
    • sourcevarchar
    • pages_viewedinteger
    • convertedboolean
    First 5 rows of web_sessions
    session_idcustomer_idstarted_atdevicesourcepages_viewedconverted
    1NULL2023-01-01 23:02:24mobilepaid1false
    2182023-01-01 15:07:49desktoppaid1false
    3NULL2023-01-01 16:55:46desktopdirect7false
    4NULL2023-01-01 12:43:28mobileorganic3false
    5NULL2023-01-01 13:06:21mobilesocial2false
    marketing_spend3,276 rows · 3 columns
    • spend_datedate
    • channelvarchar
    • amountdecimal
    First 5 rows of marketing_spend
    spend_datechannelamount
    2023-01-01paid492.99
    2023-01-01email37.38
    2023-01-01social200.53
    2023-01-02paid709.13
    2023-01-02email64.13

    The lesson

    ORDER BY sorts the result. It goes last, after FROM and WHERE:

    SELECT name, unit_price
    FROM products
    ORDER BY unit_price DESC;

    ASC (ascending, the default) sorts low to high, A to Z, oldest to newest. DESC sorts the other way. Each sort column gets its own direction.

    Tie-breakers

    Several products can share the same price. With only ORDER BY unit_price DESC, the database may put tied products in any order, and that order can change from one run to the next or between your laptop and production. For a report, that means a different list each time someone refreshes it. Add a second column to decide ties:

    ORDER BY unit_price DESC, name ASC

    The second column only matters when the first is tied. A good final tie-breaker is a unique column, such as a primary key (product_id), because then the order is fully determined. Analysts call this a deterministic sort.

    Sorting by things you did not select

    You can sort by any column of the table, even one not in the SELECT list, and by expressions:

    SELECT name
    FROM products
    ORDER BY unit_price - unit_cost DESC;

    You can also sort by an alias from the SELECT list. ORDER BY is logically evaluated after SELECT, so aliases are visible there in every major database, unlike in WHERE:

    SELECT name, unit_price * 0.9 AS sale_price
    FROM products
    ORDER BY sale_price DESC;

    Sorting by position

    ORDER BY 2 DESC sorts by the second selected column. It is handy for quick exploration and supported in Postgres, DuckDB, MySQL and BigQuery, but it breaks silently when someone inserts a column into the SELECT list. Use names in anything you save.

    Text sorts by character codes

    Text is sorted alphabetically, but the exact rules (called a collation) depend on the database. Uppercase and lowercase may sort apart, so 'oak' can land after 'Willow'. When display order of names matters, sort by LOWER(name).

    Common mistakes

    • Putting ORDER BY before WHERE. The clause order is fixed: SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY, LIMIT.
    • Sorting text that holds numbers. If a price were stored as text, '100' would sort before '9'. Check column types when a sort looks strange.
    • Assuming a table “is already sorted”. Tables have no inherent order. Only ORDER BY guarantees one.