tags:

views:

98

answers:

0
+2  Q: 

Unit of Work pattern and persistence

Hello,

I have been reading about Unit of Work pattern but I am confused about how the UoW actually persists data.

When we commit the changes, UoW should iterate through the list of Added, Updated and Deleted objects and somehow find a class responsible to Add, Update, Delete objects of a certain type.

I couldn't find an example showing this technique.

Any advice on this would be greatly appreciated.

Mosh

related questions

I'm going to write 'Unit of Work', please help me find out all gimmicks
How closely aligned is the Repository patten with either Unit of Work or ActiveRecord
Unit of Work - What is the best approach to temporary object storage on a web farm?
Using UnitOfWork with the Repository Pattern
Odd save behaviour with NHibernate and Rhino Repositories
What design pattern to locate my IUnitOfWork?
UnitOfWork pattern and atomic operations
Singleton Per Call Context (Web Request) in Unity
Datacontext and Unit of work
Unit of Work and L2S DataContext
Why would I use the Unit of Work pattern on top of an NHibernate session?
Unit of Work Design Pattern
What are the .net reference implementations of the Unit of Work pattern ?
Is Unit of Work more efficient if I don't care for transactions etc?
Nesting transaction scopes for integration tests using Rhino Commons UnitOfWork
When do i need to flush Rhino Commons UnitOfWork?
When is the last moment I can return an exception to a client in WCF?
LINQ to SQL as Unit of Work
Domain Model + LINQ to SQL sample
UnitOfWork Implementation
Unit of work question
RhinoCommons UnitOfWork Question with ASP.Net MVC
Is transactional behaviour ever needed outside of databases?
Appling Unit Of Work pattern
Unit of Work Pattern in .Net