Jul 20, 2010
The DataContext class in LINQ to SQL and the ObjectContext class in the Entity Framework are both examples of a Unit of Work.
But in our Design Pattern Framework we have not explicitly described is as the Unit of Work Pattern. The transaction model has been kept simple and all transactions are handled implicitly (Auto Commit).
The Unit Of Work pattern is particularly relevant with systems where you update multiple tables (or rows) in a single Unit of Work, that is, they all fail or all succeed. This is a common situation, but, again, it is not mentioned or referenced in Patterns in Action. However, if there is interest we can add it to our next upgrade. Any thoughts?
Jul 20, 2010
I would personally prefer explicit UnitOfWork because there are lot many chances that we update multiple tables in one call. So, we would need commit and rollback (in case of error).
Jan 14, 2011
I too would like to see an implementation of the UnitOfWork pattern.
Jan 18, 2011
I too like to see an explicit UnitOfWork Pattern.
Sep 06, 2011
I'd like to see this built into your framework in an upcoming release. I think this would be helpful as there is so much buzz regarding using this approach.
Oct 31, 2012
I would like to see this too. Has there been any update in this regard?