2 ms·
The reason is because the application knows what’s actually happening with the data.
by endisneigh 3y ago
The reason is because the application knows what’s actually happening with the data.
- LtWorf 3y agoIt's supposed to know, but it actually doesn't. At my first job they used mongodb for no reason other than it was the fad at the moment, with the big data and so on. There were often crashes in the application because our records followed several different schemas, because of bugs in the application that were later fixed, behaviour that got changed, ORM got replaced with hand written code that was much faster… Basically, what happens with over confident developers and CTO that think they are very good developers and aren't.
- endisneigh 3y agoThere are plenty of counter examples. It’s simply a fact that your application can be faster without foreign keys.
- mavelikara 3y agoYour argument, if I understand it correctly, is that the constraints can be implemented in the application layer more efficiently - either in dev time or CPU time - than it can be in the DB layer. Why is that so, and under what circumstances? (Asking to learn, not to argue)