When you say “thin data access layer”, does this mainly mean you are talking about writing your SQL manually as opposed to relying on an ORM tool to generate it for you?
Share
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.
When you say “thin data access layer”, does this mainly mean you are talking about writing your SQL manually as opposed to relying on an ORM tool to generate it for you?
Depends on how we define the word “thin”. It’s one of the most abused terms I hear, rivaled only by “lightweight”.
That’s one way to define it, but perhaps not the best. An ORM layer does a lot besides just generate SQL for you (e.g., caching, marking “dirty” fields, etc.) That “thin” layer written in lovingly crafted SQL can become pretty bloated by the time you implement all the features an ORM is providing.