3 ms·
>My rule of thumb has been: enable them strictly in DEV and INT environments, disable in PROD I mean I think the constraints should be on in all environments,
by HideousKojima 3y ago
>My rule of thumb has been: enable them strictly in DEV and INT environments, disable in PROD
I mean I think the constraints should be on in all environments, but disabling them in prod but not dev seems utterly backwards? Protect your test data from getting corrupted but not your actual customer data?
- solumunus 3y agoI assume the idea is that data corruption issues will be spotted in dev testing.
- HideousKojima 3y agoThat sounds like a terrible assumption to stake your business on though, especially for what are really marginal gains for the 99% of companies who don't need the tiny performance boost from not having foreign keys.