What's the best way to refresh entities in nhibernate

nhibernate session nhibernate-mapping refresh
Katalonis picture Katalonis · Nov 5, 2010 · Viewed 17.9k times · Source

I would like to refresh an entity and all its child collections. What is the best way to do this? I'm talking about nhibernate:)

I've read about session.Evict, session.Refresh...

But I'm still not sure if doing like:

RefreshEntity<T>(T entity)
{
 session.Evict(entity);
 session.Refresh(entity);
}

would work exactly how I want it to work

Is it going to work? If not What else I can do?

Answer

Diego Mijelshon picture Diego Mijelshon · Nov 5, 2010

Refresh after Evict probably won't work.

Theoretically, Refresh alone should be enough. However, it has known issues when elements of child collections have been deleted.

Evict followed by Get usually gets things done.

Related questions

What's the difference between session.Merge and session.SaveOrUpdate?

I notice sometimes with my parent/child objects or many-to-many relationships, I need to call either SaveOrUpdate or Merge. Usually, when I need to call SaveOrUpdate, the exception I get on calling Merge has to do with transient objects not …

Read More
NHibernate ISession Flush: Where and when to use it, and why?

One of the things that get me thoroughly confused is the use of session.Flush,in conjunction with session.Commit, and session.Close. Sometimes session.Close works, e.g., it commits all the changes that I need. I know I …

Read More
Correct use of the NHibernate Unit Of Work pattern and Ninject

I have the following implementation and would like some feedback as to whether it makes correct use of NHibernate for sessions and transactions. public interface IUnitOfWork : IDisposable { ISession CurrentSession { get; } void Commit(); void Rollback(); } public class UnitOfWork : IUnitOfWork { private readonly …

Read More