TL;DR I use two identifiers per row: a UUID as the public ID (URLs, APIs, forms) and an...
TL;DR
I use two identifiers per row: a UUID as the public ID (URLs, APIs, forms) and an auto-increment integer as the internal key (foreign keys, joins).
The bug class: those two leak into each other — a foreign key stores a UUID, a <select> posts a UUID where a key is expected, an action writes a raw key it never resolved.
The fix is a discipline: resolve UUID → key at the write boundary, and reject unknown IDs instead of inventing rows or writing nulls.
Why two IDs at all
Most developers first encounter UUIDs when setting up database primary keys. But UUIDs solve problems...
The Problem with Auto-Incrementing IDs When building a B2B SaaS platform at Smart Tech Devs, using...
I build one small browser tool a day and write down what I learned. Day 25 was a UUID generator. What...
In a previous article, I talked about Snowflake IDs. They are great, but they require a bit of...
Every backend developer types uuid() a thousand times before ever asking what those 36 characters...
How steganography solved the eternal UUID performance vs privacy dilemma in PostgreSQL
