SQL · Theory

IN

← All stacks

Theory

51/439

IN

IN sits in lab hour. Vikram’s job is a IN dry-run. Write that first.

Do IN once by hand. one IN step Vikram can write from memory. Change one input. Say the new result out loud.

IN exists so Vikram can keep a IN dry-run correct in lab hour.

IN shows up in lab hour. Name a IN dry-run, not “a real-world scenario”.

Don’t do this with IN — only reciting the name of IN. Interviewers spot it in ten seconds.

IN is not a lonely heading. Vikram ties it to a IN dry-run.

One breath for IN, then a IN dry-run, then only reciting the name of IN. Sit down.

Exam tip

Board: a IN dry-run. Dry-run IN. Name the trap: only reciting the name of IN.

IN — sample query

-- IN
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;

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

Short notes

DefIN — Vikram uses it for a IN dry-run in lab hour.
RuleIN → one IN step Vikram can write from memory.
RememberIN + InnoDB (lab hour).
UseIN in lab hour (a IN dry-run).
TrapIN — only reciting the name of IN.
ExIN → a IN dry-run.

-- IN 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;

IN

IN — sample query

Short notes

Questions

IN

IN — sample query

Short notes

Questions