Code Lab BetaBUILD. RUN. DISCOVER.
Code Lab is in development. New lessons and improvements are on the way. Progress can be deleted.
Loading…
Code Lab is in development. New lessons and improvements are on the way. Progress can be deleted.
Loading…
Code Lab is in development. New lessons and improvements are on the way. Progress can be deleted.
SQL / POSTGRESQL / Learn / LESSON 08
PostgreSQL lets RETURNING follow INSERT/UPDATE/DELETE to return affected rows immediately. That is handy for apps. In Code Lab, grading checks the final table state — not RETURNING output alone.
Small example:
INSERT INTO items (id, name, category, qty, price) VALUES (94, 'X', 'tools', 1, 1) RETURNING id, name;
Starting tables for this task. Grading checks final state on other datasets too.
| id | name | category | qty | price |
|---|---|---|---|---|
| 1 | Pen | tools | 10 | 1.5 |
| 2 | Notebook | books | 5 | 3 |
| 3 | Mug | home | 2 | 8 |
| 4 | Sticker | NULL | 0 | 0.5 |
| 5 | Lamp | home | 1 | 25 |
| 6 | Book Atlas | books | 3 | 12 |
Expected verify columns: id, name, category, qty, price · row order is checked
Expected final state (displayed data):
Loading…PostgreSQL lets RETURNING follow INSERT/UPDATE/DELETE to return affected rows immediately. That is handy for apps. In Code Lab, grading checks the final table state — not RETURNING output alone.
QUERY STANDBY
›