SQL · Theory

Interview

← All stacks

Theory

114/439

Interview

Don’t start Interview with jargon. Start with a fail-list view. That is the whole point.

Interview order — meaning → CREATE VIEW fail_list AS … → one limit. Dumping ten features helps nobody.

Skip Interview and trying to UPDATE a non-updatable view shows up in teachers’ report.

Farhan ships Interview in teachers’ report. That is the use case worth saying.

Don’t do this with Interview — trying to UPDATE a non-updatable view. Interviewers spot it in ten seconds.

After Interview, Farhan should still remember trying to UPDATE a non-updatable view.

One breath for Interview, then a fail-list view, then trying to UPDATE a non-updatable view. Sit down.

Exam tip

Say Interview in one breath, then CREATE VIEW fail_list AS …, then trying to UPDATE a non-updatable view.

Interview — sample query

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

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

Short notes

DefInterview — Farhan uses it for a fail-list view in teachers’ report.
RuleInterview → CREATE VIEW fail_list AS ….
RememberInterview + the query planner (teachers’ report).
UseInterview in teachers’ report (a fail-list view).
TrapInterview — trying to UPDATE a non-updatable view.
ExInterview → a fail-list view.

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

Interview

Interview — sample query

Short notes

Questions

Interview

Interview — sample query

Short notes

Questions