Database
Lætitia AVROT: Region : a lesson in data integrity
Planet PostgreSQL0 views
Yesterday, a colleague of mine opened a simple PR. The business needed a region on an existing table, so he added a text column to hold it. Clean, small, ready to review and merge. Database internals? No problem. This was going to be a five-minute approval. I did not approve it. Not because the code was wrong. The code was fine. I challenged the content: why a free-text column? Why not a domain, an enum, a text column with a check constraint, or a reference table?
Source：https://postgr.es/p/9zBPreviousChristophe Pettus: Binary read replicas in PostgreSQL, Part 3NextResearchers thread the world's first touchscreen into a garment
Related posts
Postgres LISTEN/NOTIFY vs Redis Pub/Sub: Latency, Write Cost and Failure Cases, Tested
0dev.to Node
LlamaIndex Workflows vs LangGraph: Event-Driven Architecture and Async State Overhead Showdown
0dev.to Programming
Rider and Databases: Lesser-Known IDE Features That Save Time
0dev.to Database
KivaDB v2: What's Coming and How You Can Contribute
0dev.to Database
Your LLM cost log says $0.00. The invoice says $1,320.
0dev.to Database
SQLite in Production: A Practical Setup with Litestream Backups
0dev.to Database