Your Code Assumes Every UUID Is Random
For years a UUID meant version 4. One hundred and twenty two random bits, and a few fixed ones saying what kind it was. So code grew up around that…
Последние новости
⚑ Сообщить о проблемеTech news from the best sources
Все темы
AI
Gear
News
Tech
agents
ai
api
architecture
automation
beginners
career
database
devchallenge
devops
discuss
javascript
llm
machinelearning
mcp
opensource
performance
productivity
programming
python
security
showdev
testing
tutorial
typescript
webdev
UUID v4 vs. UUID v7 vs. ULID in 2026: Database Index Performance, B-Tree Fragmentation & When to Migrate
UUID v4 vs. UUID v7 vs. ULID in 2026: Database Index Performance, B-Tree Fragmentation, Collision Mathematics, and RFC 9562 Migration Guide For more…
UUIDs explained — the uniqueness myth, the version you should be using, and the database mistake that slows everything down
You've generated thousands of UUIDs without thinking twice. id column, default value, done — a 36-character string that looks like f47ac10b-58cc-437…
🚀 I Built UUIDs That Look Random But Sort Like Timestamps (50% Smaller Indexes!)
TL;DR Built a PostgreSQL extension that creates UUIDs looking like random v4 but containing hidden timestamps. Result: 50% smaller indexes with perf…
Stop using UUID v4 as your database primary key
I spent a while wondering why inserts on a particular table were getting slower as it grew. The table had a UUID v4 primary key and a few indexes. T…