In the hibernate documentation:
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/
there is this advise about using DAO:
<quote>
Consider abstracting your business logic from Hibernate.
Hide (Hibernate) data-access code behind an interface. Combine the
DAO and Thread Local Session patterns. You can even have some classes
persisted by handcoded JDBC, associated to Hibernate via a UserType.
(This advice is intended for "sufficiently large" applications; it is
not appropriate for an application with five tables!)
</quote>
So when should i consider using DAO? What is considered a "sufficiently
large" application?
According to the quote above, five tables is not. But what is?
Is a 20 table app a sufficiently large one? 50? 200?
Any help is a appreciated.
Luke Webber - 19 Mar 2006 23:39 GMT
> In the hibernate documentation:
>
[quoted text clipped - 19 lines]
>
> Any help is a appreciated.
My advice would be that a five-table app is probably not sufficiently
large or complex to require Hibernate, but might still benefit from DAO. <g>
Luke