Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp
Hi,

I'm using NH 1.2 , and i'm trying to do : session.Lock(entity,LockMode). The problem i'm having , is that there's no way I can find to check if the entity has already been attached to the session.

I found an IsSaved method, but it's in SessionImpl class. When i reattach an already attached entity it throws an error ( cause it just couldn't fail silently? ). The solution for now is a try{}catch{} - and leaving it like that would suck.


Another question I have is : How can I force NH to not load a subentity from cache. (like Client.ClientDetails - ClientDetails does not have the update-ed information. )
.

I think ISession.Contains(object entity) can help you check whether your entity is already in the session.

Cheers,

Symon.

Hmm, thanks, didn't see that :).

My problem turned out to be another, I tried lock on a new entity , that had never been saved previously :|.

Thanks for the help mate.


And for my second question : How can I force NH to not load a subentity from cache. (like Client.ClientDetails - ClientDetails is loaded from Cache).

You could use SaveOrUpdateCopy() rather than Lock(), that would let you give it either a transient or persistent entity, but we had problems with it (well over a year ago so I don't remember the details). For separate reasons we track whether an entity is transient or not ourselves, so we know whether to call Lock() or Save(). If you don't use assigned IDs, you could just check if the ID property has a value to know if it's transient or not.

I think that if you use assigned identifiers this should still work as long as you implement a version property.

Cheers,

Symon.

Thanks for the info, for now Lock will do just fine. I already said that it was a simple mistake not checking if the entity was new or not .

How about the lazy loading thingy ?

An unwise way would be to clear the cache, but that brings you in a lot of new troubles

Well, that's the only way I could do it up to this point. So if I can't find another way ..... Clear() will remain the only way :|