session.Load<Customer>(5); // doesn't hit the db, so we don't HAVE any way to provide those values. session.Get<Order>(15);// we need to provide a value for Order.Customer, but we don't want to load that data
2008/12/30 Krzysztof Koźmic <[email protected]> > Do you mean proying dependencies for lazy loading? so that instead of > CustomerName instance I get a proxy? > Can you elaborate on that? I'm not sure I understand your answer. > > Krzysztof > > Ayende Rahien pisze: > > Proxies > > On Tue, Dec 30, 2008 at 11:33 PM, Krzysztof Koźmic < > [email protected]> wrote: > >> Greg Young pisze: >> >> Fabio this discussion has already happened and I prefer to not restate >> the same positions as before but ... in terms of insuring correctness >> assuming that data from the database is correct is a nefarious at best >> course of action. >> >> >> True, especially if you consider schema changes or access to DB >> bypassing the app. >> I mean, aside from how NH is currently implemented - how is having *only >> *non-default .ctor and required value type dependencies a bad idea? >> >> Krzysztof >> >> On Tue, Dec 30, 2008 at 11:31 AM, Fabio Maulo <[email protected]> >> <[email protected]> wrote: >> >> >> 2008/12/30 Greg Young <[email protected]> <[email protected]> >> >> To not be able to insure validity upon construction is a very large cost. >> >> >> Really not for me; the default ctor is private and used only for upload from >> persistence. >> -- >> 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 -~----------~----~----~----~------~----~------~--~---
