No answers. Mmmhh.
I mean: do you use in your programs the GenericDAO<T, ID> (e.g. var
dataSource = (new someEntityDAO()).GetRightEntities())?
Or do you prefer to directly write in your (Web)Forms code like:
var dataSource = CurrentSession.CreateQuery("from someEntity e
where...");
Thanks again,
marcello.
On 28 Apr, 22:22, Marcello Esposito <[email protected]> wrote:
> Hi all.
>
> In NHibernate in Action, last chapter, the authors present the
> GenericDAO<T, ID> pattern.
>
> It looks very clean to me.
>
> When approaching to write a brand new architecture for a non-trivial
> information system, would you systematically use this pattern for all
> the involved persistent classes? Are there some disadvantages in doing
> so?
>
> Can this pattern hide NHibernate machinery behind the persistency
> layers thus avoiding to completely exploit its functionalities (e.g.
> ToFuture())?
>
> Thanks in advance,
> marcello esposito.
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
