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.
Most(if not all) of the MVC frameworks provide an abstraction layer over the database and except in some very special cases you do not need to write SQL code by hand. Of course you need to know basic things to design your model but do we need deep knowledge how to optimize queries, make triggers and other db stuff.
Not unless your the one writing the the code for the data abstraction layer.
That’s the whole point of it. Any layer above it doesn’t need to know what the database type or structure is, or even if there is one.
It is a common mistake to start dragging database specific stuff back across the data layer into the business logic.
The acid test is that if you changed your database say from SQL to Oracle or MySQL would the rest of the code still work. If not then your data layer isn’t doing its stuff correctly.