Case Studies
Adding a Foreign Key to a Legacy Orders Table Full of Orphan Rows
This one comes up whenever an old application gets a second look. The orders table has a customer_id column. It has always pointed at customers.id. Nobody ever declared …
Tag
Case Studies
Case Studies
Adding a Required Column to a Busy PostgreSQL Table and What Happens to Old Rows
An online shop wants three new columns on orders. A status that every order must have. A fulfilled_at timestamp. And a public_id uuid to show customers instead of the …
Case Studies
Adding a Unique Email Constraint to a Customers Table That Already Has Duplicates
Here’s a scenario almost every product team hits sooner or later. Sign-up has been running for two years. Somebody finally notices that customers.email was never …
Case Studies
Building an Index on a Large PostgreSQL Table Without Freezing the Rest of the App
Reporting is slow. The query behind the monthly dashboard filters events by account and date, and events is by far the biggest table in the database. Everyone agrees it …
Case Studies
Catching PostgreSQL Schema Drift in CI With ForgeSchema Verify
Picture a team with three environments: development, staging and production. The schema lives in a YAML file in the repository, and everyone agrees that file is the …
Case Studies
How ForgeSchema Blocks an Accidental Column Drop From a Bad Merge
Two branches both touched schema/app.yaml. One added a phone column to customers. The other moved a few columns around for readability. Git resolved the conflict, the …
Case Studies
Renaming a PostgreSQL Column Without Losing Data in ForgeSchema
A small team is tidying up an old schema. The customers table has a column called customer_name, which is redundant inside a table called customers. They want full_name. …
Case Studies
Why ForgeSchema Refuses a Migration Plan Made Stale by an Overnight Hotfix
Monday afternoon, a developer builds a migration plan. It adds a notes column to customers and an index on it. Two colleagues review it, approve it, and it’s …