Master DAO or many DAOs ?

[Hussein Baghdadi]

Hi.
In my application, I have domain objects like : Book, Author, Publisher (I'm using Hibernate)....
I created interfaces like BookDAO, AuthorDAO and then implement them using HibernateDaoSupport.
But while I'm coding my DAO's, a question came into my mind :
Is it good to many DAOs (like my case) or to create a master DAO called for example :
BookStoreDAO ?
What is the right approach here ?
Thanks folks

[Jeanne Boyarsky]

John,
There is no right or wrong here. It's a matter of personal preference.

[Jaime M. Tovar]

I recomend many daos if you are planning to reuse your code. You can just take the things you need and leave everything else out of your new project. It is also easier to work when you are doing maintenance because you know exactly in which dao you need to do the corrections.
Well just my opinion.

[Mr. C Lamont Gilbert]

I have both many daos and then a master dao that most others are obtained from. but that master dao is not really a dao then since its not really about data access but dao access

[Pavel Kubal]

I would like to add, that there's no wrong and right. There is better and worse (or equal :-) ). And it really depens on what is the target scope.

But from you description, I incline to many DAOs.