Work structure and persistence
I've read about the Unit of Work pattern, but I'm confused about how UoW actually saves data.
When we commit changes, UoW must go through the list of added, updated and deleted objects and somehow find the class responsible for adding, updating, removing objects of a certain type.
I couldn't find an example to demonstrate this technique.
Any advice on this matter would be greatly appreciated.
Mosh
+2
a source to share
1 answer
Check this post: Work Design Unit
which points to this link: http://www.codeinsanity.com/2008/09/unit-of-work-pattern.html
0
a source to share