title: More confused than ever with units of work vs. none and dodging micro-management of Transactions in Repository!
body: <p>I had come to the conclusion that there was no reason to use a UnitOfWork on top of a NHibernate session and was asking in <a href="https://stackoverflow.com/questions/5869896/need-help-understanding-nhibernate-transactions-and-how-not-to-duplicate-code-if">this question</a> on the best way not to have to explicitly create a transaction for every database persistence action.  </p>
  
  <p>Only to be redirected back to the idea of a Unit of Work.  Well, further investigation has lead me back to where I was originally not to implement a separate Unit of Work pattern on top of NHibernate (one <a href="http://ayende.com/Blog/archive/2010/07/30/the-false-myth-of-encapsulating-data-access-in-the-dal.aspx" rel="nofollow noreferrer">example</a>, amongst others).  </p>
  
  <p>My problem is how do you not use a Unit of Work, AND not micro-manage a transactions in a repository and keep it separate?</p>