Keep the first row for each staging key
Your task
Create a staging table with code as its primary key and units as an integer. Attempt to insert ('A', 2), ('A', 9), and ('B', 4) in that order, skipping duplicates. Return code and units sorted by code.
OR IGNORE can skip a row whose key matches one already inserted.
Expected output
| code | units |
|---|---|
| A | 2 |
| B | 4 |
Show a hint
Make code unique and use INSERT OR IGNORE to keep the original A row.
Writing and modeling data guide
Define the shape of a table
A primary key identifies a record. NOT NULL makes a value mandatory, and CHECK restricts allowed values. Put these rules in the table definition so SQLite enforces them on writes. The PRAGMA query below inspects the column declarations.
CREATE TABLE deliveries (
id INTEGER PRIMARY KEY,
album_id INTEGER NOT NULL REFERENCES albums(id),
copies INTEGER NOT NULL CHECK (copies > 0)
);
PRAGMA table_info(deliveries);Preview the rows before changing them
In an update or delete, WHERE determines which rows change. Try the same condition in a SELECT first. The write exercises start from a fresh practice database on each run, so include all the needed statements in one submission.
SELECT id, title, stock FROM albums WHERE id = 3;
UPDATE albums SET stock = stock + 5 WHERE id = 3;
SELECT id, title, stock FROM albums WHERE id = 3;Group changes into a transaction
BEGIN starts a transaction. COMMIT keeps its changes and ROLLBACK undoes them. Here the final SELECT shows the original stock because the UPDATE was rolled back.
BEGIN;
UPDATE albums SET stock = 0 WHERE id = 1;
ROLLBACK;
SELECT title, stock FROM albums WHERE id = 1;Worked solution
CREATE TEMP TABLE staging(code TEXT PRIMARY KEY,units INTEGER); INSERT OR IGNORE INTO staging VALUES ('A',2),('A',9),('B',4); SELECT code,units FROM staging ORDER BY code;Press Control+Space for SQL suggestions. Use the arrow keys to select an option and Enter to insert it.
Results
Loading SQLite…
