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.
DISCLAIMER: I’m almost sure that I’ve seen the same question before but I can’t find it now. If someone finds that question, please, give a link.
I heard at least two opinions on the best name for classes which implements CRUD operations: someone says that DAO is a classical name and everyone knows what it means, but others say that Manager corresponds much better to CRUD functionality.
Are there any unambiguous rules when should I choose one or another (or yet another) name?
I definitely don’t like Manager; “managing” something could mean (and is used to mean) all kinds of things. If you’re afraid people won’t know what DAO means, you could always spell it out as “DataAccess”, say. But I find DAO to be widely understood.
Another approach is to use the Repository pattern and call your class SuchAndSuchRepository. This isn’t necessarily the same thing as a DAO (it may wrap one or more DAOs) but it can provide a clearly named place to go to get your objects — if I want a Person object, I know to look for the PersonRepository.