migrations – Page 8 – Türker Yıldırım

OPTIMIZE TABLE is a rebuild wearing a friendly name

NoteDecember 8, 20222 min read

For InnoDB, OPTIMIZE TABLE is mapped to an ALTER TABLE … FORCE, which copies the whole table. The friendly name is the problem: it sounds like a maintenance…

Importing what already exists, one resource at a time

NoteNovember 11, 20222 min read

Adopting Terraform on existing infrastructure is mostly import, and import brings a resource into state without writing any configuration for it. One resource, one commit, one empty plan…

An idempotent consumer for a broker that redelivers

Deep diveNovember 8, 202210 min read

A message processed twice, and a customer charged twice. At-least-once delivery, treated as exactly-once by the handler.

Two teams, one database, and the schema change that needed a meeting

Deep diveOctober 29, 202210 min read

A shared schema, and a rename that took three weeks to coordinate. Table ownership that exists in nobody’s head.

CHECK constraints are enforced from 8.0 and ignored before

NoteOctober 20, 20221 min read

MySQL 5.7 parses a CHECK constraint, stores it and never evaluates it, which is worse than rejecting it. A constraint that exists and does nothing is the worst…

MySQL 8.0.30 generated invisible primary keys

NoteOctober 10, 20222 min read

October’s point release can add a hidden primary key to a table created without one, which matters for replication and for group replication in particular. A table without…

The database that was 80% dead rows

Deep diveOctober 4, 202210 min read

180 GB on disk and 41 GB of data. A table that was deleted from daily and never shrank.

The API version that was never going to be removed

Deep diveSeptember 21, 202215 min read

v1, v2 and v3 in production, and v1 has four clients. Every change is made three times.

Bootstrap 5.2, CSS variables, and a theme that stopped being a fork

Deep diveAugust 17, 202210 min read

5.2 in July, and custom properties throughout the components. A Sass fork that had to be rebased on every patch release.

Vite 3 moved the dev server port

NoteJuly 28, 20222 min read

The default port changed from 3000 to 5173, which breaks every script, proxy rule and README that had the old one written down. strictPort is the setting worth…