webcoderspeed.com
3 articles
You add ON DELETE CASCADE to a foreign key. You delete a test organization. It cascades to users, which cascades to sessions, orders, invoices, activity_logs — 10,000 rows gone in milliseconds. No warning, no undo. Cascade deletes are powerful and dangerous.
You store a price as a JavaScript float. You retrieve it as 19.99. You display it as 20.000000000000004. Or you store a BigInt user ID as JSON and it becomes the wrong number. Serialization bugs corrupt data silently — no error, just wrong values.
Your server is in UTC. Your database is in UTC. Your cron job runs at "9 AM" — but 9 AM where? Customer in Tokyo and customer in New York both get charged at your server''s 9 AM. Your "end of day" reports include data from tomorrow. Timezone bugs are invisible until they''re expensive.