SQL · Theory

OR

← All stacks

Theory

47/439

OR

OR is a SQL idea you prove with OR on Rohit's board, not with a slogan.

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

Without OR, a viva board gets messy and OR on Rohit's board is hard to trust.

OR shows up in a viva board. Name OR on Rohit's board, not “a real-world scenario”.

OR trap — copy-pasting OR without a dry-run. Rohit loses marks for that every viva.

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

Close OR with — “If I skip it, OR on Rohit's board goes wrong like this: copy-pasting OR without a dry-run.”

Exam tip

Board: OR on Rohit's board. Dry-run OR. Name the trap: copy-pasting OR without a dry-run.

OR — sample query

CREATE TABLE products (id INTEGER PRIMARY KEY, name TEXT, price REAL);
INSERT INTO products VALUES (1, 'Pen', 10), (2, 'Book', 200), (3, 'Bag', 50);
SELECT * FROM products
WHERE price BETWEEN 20 AND 150 AND name LIKE 'B%';

OR — wHERE combines predicates with AND/OR; LIKE does pattern match.

Short notes

DefOR — Rohit uses it for OR on Rohit's board in a viva board.
RuleOR → one OR step Rohit can write from memory.
RememberOR + InnoDB (a viva board).
UseOR in a viva board (OR on Rohit's board).
TrapOR — copy-pasting OR without a dry-run.
ExOR → OR on Rohit's board.

CREATE TABLE products (id INTEGER PRIMARY KEY, name TEXT, price REAL); INSERT INTO products VALUES (1, 'Pen', 10), (2, 'Book', 200), (3, 'Bag', 50); SELECT * FROM products WHERE price BETWEEN 20 AND 150 AND name LIKE 'B%';

OR

OR — sample query

Short notes

Questions

OR

OR — sample query

Short notes

Questions