SQL · Theory

Workbench

← All stacks

Theory

97/439

Workbench

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

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

Without Workbench, a viva board gets messy and a Workbench dry-run is hard to trust.

Dev ships Workbench in a viva board. That is the use case worth saying.

Workbench trap — skipping the failure case for Workbench. Dev loses marks for that every viva.

After Workbench, Dev should still remember skipping the failure case for Workbench.

Close Workbench with: “If I skip it, a Workbench dry-run goes wrong like this: skipping the failure case for Workbench.”

Exam tip

For Workbench: definition + a viva board + one failure.

Workbench — sample query

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

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

Short notes

DefWorkbench — Dev uses it for a Workbench dry-run in a viva board.
RuleWorkbench → one Workbench step Dev can write from memory.
RememberWorkbench + the query planner (a viva board).
UseWorkbench in a viva board (a Workbench dry-run).
TrapWorkbench — skipping the failure case for Workbench.
ExWorkbench → a Workbench dry-run.

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

Workbench

Workbench — sample query

Short notes

Questions

Workbench

Workbench — sample query

Short notes

Questions