I agree with that, but as you said it doesn't matter the ORM you are using or its features at that stage.Hibernate goal was, from the site, to relieve the developer from 95 percent of common data persistence related programming tasks, compared to manual coding with SQL and the JDBC API.
NH can be as the same on top of ADO.NET. What you are looking for is a feature that it is not persistence so NH won't help, you have to deal with a framework which will take care of more layers than the persistence layer. That framework may or may not use NH at the persistence layer. Gustavo. 2009/6/20 Yevhen Bobrov <[email protected]> > > It is. It is not about NH problem but about what happens when changes > are applied directly to the object and there is need to cancel them. > This is what happens in usual WinForms application. > > On 20 июн, 18:15, Fabio Maulo <[email protected]> wrote: > > 2009/6/20 Yevhen Bobrov <[email protected]> > > > > > > > > > BTW, Frederik talks about such kind of problem here > > > > >http://fgheysels.blogspot.com/2009/06/winforms-databinding-on-cancell. > .. > > > > That is not a post about a problem, that is a post about a UI solution > and > > as you can see there is no reference about the persistent-layer and no > > reference about the usage of Clone. > > Frederik had the good spirit, even showing the n-level-undo capability of > > CSLA (where, another time, the persistence-layer has nothing to do). > > > > We'll wait your example showing your problem in detail; after have it we > can > > talk about a solution if you can't find it. > > > > -- > > Fabio Maulo > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
