Nhibernate isession.save return value


I think it won't, because NHibernate wouldn't be able to create a proxy. Another way to solve a problem with lazy load and Null objects is to have 2 sets of properties: one set for public usage and another for NHibernate only. NHibernate only properties will be mapped as usual properties and lazy would work fine on them. One of the nicest new features in NHibernate 2.1 is the Future<T>() and FutureValue<T>() functions. They essentially function as a way to defer query execution to a later date, at which point NHibernate will have more information about what the application is supposed to do, and optimize for it accordingly. I am using Visual Studio 2008 with NHibernate 2.1.0.4 to access MySql 5.0.67. I am finding that when I call ISession.Save(organisation) that the Id is not being returned correctly. Worse still, the failure to return a correct Id affects the automatically generated step to insert OrganisationCapability records. I think it won't, because NHibernate wouldn't be able to create a proxy. Another way to solve a problem with lazy load and Null objects is to have 2 sets of properties: one set for public usage and another for NHibernate only. NHibernate only properties will be mapped as usual properties and lazy would work fine on them. [nhibernate-issues] [JIRA] Created: (NH-958) ISession.SaveOrUpdateCopy throws exception when class has <any> mapping Oct 31, 2007 · The all-delete-orphan value indicates that NHibernate should cascade all saves and deletes, and that it should delete any orphans that are left as a result of deletion. Note that the cascade style must be specified in any association mapping, or NHibernate will not cascade saves and deletes.