- MySQL – INFORMATION_SCHEMA
Querying the database about itself. TABLES, COLUMNS, STATISTICS, KEY_COLUMN_USAGE and REFERENTIAL_CONSTRAINTS, finding every foreign key pointing at a table before you drop it, listing indexes that duplicate each other, estimating table and index size on disk, why TABLE_ROWS is an estimate and not a count, and how SHOW commands map onto the same data.
- LeetCode 119 – Pascal's Triangle II
One row, in O(k) space, which turns a warm-up into a real exercise in updating an array without destroying what you are about to read. Sweep right to left so the stale values survive — the same rule that separates 0/1 knapsack from unbounded, and the question is always which values the cell needs.
- MySQL – Scheduled Events
Cron inside the database. The event_scheduler variable that is OFF by default so your first event never runs, CREATE EVENT with AT and with EVERY, STARTS and ENDS, ON COMPLETION PRESERVE, altering and disabling one, where errors go, what happens on a replica, and the question to settle first — whether this belongs in the database at all or in the scheduler you already operate.
- LeetCode 118 – Pascal's Triangle
The gentlest bottom-up DP there is, and on the list as the setup for its follow-up. The edges are where the rule runs out of inputs rather than a special case bolted on, the output size IS the complexity so there is nothing to optimise — which is exactly why problem 119 asks for one row.
- MySQL – Triggers
Running a statement automatically when a row changes. BEFORE and AFTER, INSERT, UPDATE and DELETE, the NEW and OLD rows, writing an audit trail, keeping a derived total in step, the limitations that bite — a trigger cannot touch its own table, and it does not fire for TRUNCATE — and the real argument against them: logic that runs invisibly is logic nobody debugging your application will think to look for.