Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
http://www.percona.com/ppc2009/PPC2009_Boring_MySQL.pdf:
Don’t do work in the database if you can do it elsewhere
I must say I don’t quite understand this statement. Can someone elaborate on it?
Does it mean the we should enforce integrity on the application level instead of at the database level?
Or does it mean something else completely?
We have no way of knowing. The only person who knows what he meant by that is the author, Baron Schwartz. A quick scan of his slides suggests he isn’t an idiot, so I’m pretty sure he doesn’t mean enforce integrity in the application not the database. He probably means don’t overload the database with other processing that can be done more efficiently elsewhere.