SQL · Theory

SET

← All stacks

Theory

300/439

SET

Don’t start SET with jargon. Start with a SET dry-run. That is the whole point.

For SET, the query planner is in play. Don’t blame it until you have traced a SET dry-run.

Skip SET and only reciting the name of SET shows up in a first job task.

Farhan ships SET in a first job task. That is the use case worth saying.

SET trap — only reciting the name of SET. Farhan loses marks for that every viva.

Place SET next to nearby SQL work — one SET step Farhan can write from memory is the link.

Viva for SET — what it is → one SET step Farhan can write from memory → the mistake (only reciting the name of SET).

Exam tip

Say SET in one breath, then one SET step Farhan can write from memory, then only reciting the name of SET.

SET — sample query

-- SET
CREATE TABLE demo (
  id INTEGER PRIMARY KEY,
  label TEXT NOT NULL,
  qty INTEGER DEFAULT 0
);
INSERT INTO demo (id, label, qty) VALUES
  (1, 'alpha', 2),
  (2, 'beta', 5);
SELECT label, qty FROM demo WHERE qty >= 2 ORDER BY qty DESC;

SET: create two demo rows, then SELECT qty >= 2 ordered. Say which labels come back.

Short notes

DefSET — Farhan uses it for a SET dry-run in a first job task.
RuleSET → one SET step Farhan can write from memory.
RememberSET + the query planner (a first job task).
UseSET in a first job task (a SET dry-run).
TrapSET — only reciting the name of SET.
ExSET → a SET dry-run.

-- SET CREATE TABLE demo ( id INTEGER PRIMARY KEY, label TEXT NOT NULL, qty INTEGER DEFAULT 0 ); INSERT INTO demo (id, label, qty) VALUES (1, 'alpha', 2), (2, 'beta', 5); SELECT label, qty FROM demo WHERE qty >= 2 ORDER BY qty DESC;

SET

SET — sample query

Short notes

Questions

SET

SET — sample query

Short notes

Questions