2010/7/12 Fabio Maulo <[email protected]>: > On Mon, Jul 12, 2010 at 8:28 AM, Oskar Berggren <[email protected]> > wrote: >> >> Then of course, there may be nhibernate-isms "leaking" through, even >> when you don't have direct usage of the API. >> > > The only I have found is due to Auto-Dirty-Check on Flush. > Have you something else ? > I'm interested, really.
No, not a list of "issues". I was more referring to the potential risk and that you expect a certain behavior from your persistance. That is, even if direct API use is limited, it doesn't mean you can replace it with _anything_ else. You would probably still need something with a fairly similar feature set. Of course, nothing strange with that. (E.g. if you design with lazy load in mind, you might get bad performance if you suddenly cannot use lazy.) /Oskar -- 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.
