UoW, Repository and EF

Given UoW:
"Maintains a list of objects affected by a business transaction and coordinates the writing out of changes and the resolution of concurrency problems."
and Repository:
"Mediates between the domain and data mapping layers using a collection-like interface for accessing domain objects."

Why do you think it’s useful to apply UoW and the Repository pattern to EF?

I think the DataContext in EF IS a UoW in some way, and an EF entity IS a Repository.
Agree, UoW patter is helpful in a complex scenario with multiple contexts, with different connections.
What do you think about it?

answer here please:
http://stackoverflow.com/questions/4146979/uow-repository-and-ef

 

[update]
References:
http://blogs.microsoft.co.il/blogs/gilf/archive/2010/06/21/revisiting-the-repository-and-unit-of-work-patterns-with-entity-framework.aspx
http://msdn.microsoft.com/en-us/magazine/dd882510.aspx

Advertisements

2 thoughts on “UoW, Repository and EF

  1. hi Frank,
    unfortunately the guys at stackoverflow thought my question was not intelligent enough and they removed it 🙂

    not many feedback unfortunately so this remain an open question

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s