Attaching a disconnected object to an NHibernate session; best practice?

Question

My repository works in a UnitOfWork model; all operations, whether retrieval or persistence, must be performed within the scope of an IDisposable <

Answer 1

D: None of the above. Effectively disabling lazy-loading by keeping your UOW too short and defeats the purpose of a lazy-loading ORM. The fact that you have to re-associate disconnected objects as normal operations means that your unit of work boundaries are wrong.

Merge, Update, and Lock all have different purposes. If you're stuck with your current architecture then Lock is probably what you want.

• Update - associates a changed object
• Lock - associates an unchanged object
• Merge - if the object exists in the current session then it is updated with changes from the merged object, otherwise it's the same as Lock