CURRENT_TIMESTAMP()
CURRENT_TIMESTAMP() is simple if you keep it on paper. Priya uses it for Priya walking through CURRENT_TIMESTAMP in lab hour.
CURRENT_TIMESTAMP() on the board: one CURRENT_TIMESTAMP step Priya can write from memory. Then say what Priya walking through CURRENT_TIMESTAMP looks like after.
CURRENT_TIMESTAMP() exists so Priya can keep Priya walking through CURRENT_TIMESTAMP correct in lab hour.
CURRENT_TIMESTAMP() shows up in lab hour. Name Priya walking through CURRENT_TIMESTAMP, not “a real-world scenario”.
If Priya walking through CURRENT_TIMESTAMP breaks under CURRENT_TIMESTAMP(), check copy-pasting CURRENT_TIMESTAMP without a dry-run first.
Place CURRENT_TIMESTAMP() next to nearby SQL work — one CURRENT_TIMESTAMP step Priya can write from memory is the link.
Viva for CURRENT_TIMESTAMP(): what it is → one CURRENT_TIMESTAMP step Priya can write from memory → the mistake (copy-pasting CURRENT_TIMESTAMP without a dry-run).
For CURRENT_TIMESTAMP(): definition + lab hour + one failure.