- MySQL – CREATE TABLE, Constraints and ALTER
Writing the schema. CREATE TABLE column by column, PRIMARY KEY and why the pizza tables use a surrogate BIGINT, NOT NULL and DEFAULT, UNIQUE constraints and what they buy that application code cannot, FOREIGN KEY with ON DELETE CASCADE versus SET NULL — a choice the order tables make both ways on purpose — CHECK constraints, AUTO_INCREMENT, and ALTER TABLE on a table that already has rows in it.
- MySQL – Date and Time Types
DATE, TIME, DATETIME, TIMESTAMP and YEAR, and the one difference that matters: TIMESTAMP converts to and from the session time zone and DATETIME does not. Why the pizza schema stores DATETIME(6), what the fractional-seconds argument buys you, the 2038 problem TIMESTAMP still has, DEFAULT CURRENT_TIMESTAMP and ON UPDATE, and how to store an instant so it survives a server moving between time zones.
- MySQL – Data Types
Picking the right column type, and the two that cost real money to get wrong. INT versus BIGINT and what AUTO_INCREMENT actually runs out of, why every price column in the pizza schema is DECIMAL(10,2) and never FLOAT, VARCHAR versus CHAR and what the length really limits, TEXT and BLOB, ENUM and why the schema uses VARCHAR instead, BOOLEAN being TINYINT(1) in disguise, and utf8mb4 — the reason MySQL's own `utf8` cannot store an emoji.
- MySQL – Connections, URLs and Pooling
How an application actually talks to MySQL. Reading a JDBC URL parameter by parameter, why `serverTimezone` and `allowPublicKeyRetrieval` exist and when you need them, connection pooling with HikariCP and how to size a pool, `wait_timeout` and the stale-connection errors it causes overnight, and `max_connections` — the limit you meet on a bad day rather than a good one.
- AWS – IAM: Policies, Roles and Least Privilege
IAM is the service you get wrong first and it is the one that matters most. The five parts of a policy document, the difference between an identity policy and a resource policy — and why an S3 bucket needs both — roles versus users and why your code should never hold a key, and how a deny always wins. Ends with the real bucket policy that lets exactly one CloudFront distribution read this site and nothing else.