Problems when accessing lists through property

Thanks Fabio,

We have tested this on our systems and the Refresh function behaved as we would expect it to.

I added and removed items to the collections after the load and before the refresh, as well as updated property values to see if refresh reloaded the objects from the db. It did in all cases.

It is confirmed that the collections are all loaded on refresh, even when lazy loading is enabled, the property setter can still access the Count on the object, the tests pass and I think that satisfies our requirement.

Cheers,
Dave

This is the comment of Refresh method:
It is unadvisable to use this to implement long-running sessions that span many business tasks. This method is, however, useful in certain special circumstances.

You are using Refresh to reattach a detached entity where Refresh was implemented only for some special case and only for attached entities.
In practice, in your case, you should use a Get<T>.

Btw I'll take a look to check what happening and understand if we can support Refresh even for detached entities.

Hi Fabio,

We are trying to cancel changes made to the domain. We need to refresh from the last saved state in the database and then rollback the state to the one in the database.

So we wish to refresh(), then transaction.rollback(). However, we can't get past the refresh() when there are collections assigned in the way we have shown.

Here is the use case:

• user makes changes which are reflected in the domain objects

• user decides not to commit the changes (decides to cancel changes, or decides to revert because they are unable to get a write lock, etc.)

• user wishes to revert changes to domain objects (not reload, because the object graph is quite large)

Does that help explain the use case?

Cheers,
Dave

I still don't understand why you need to do that...
Why you need to change the fresh state loaded from db...
Really can't understand the use-case.
I can understand that you need to change something that don't become from DB but really I can't understand your case.

Hi Fabio,

We are retrofitting our existing system to use nHibernate. Our existing system contains examples of this kind of arrangement. Our existing system updates state variables when new properties are assigned.

We have modified the test case so there is an additional test case. The additional test case demonstrates an exception with one list that is not lazy loaded. Note that when there are multiple lists, the second and third list can access the Count property without it failing. We have also changed the original test so that nothing is lazy-loaded.

We are confused about how we should use the where clause. We don't think adding a where clause would solve the problem in the case where there is one list.

Regards,
Dave