Repository vs Data Access
- by vdh_ant
Hi guys
In the context of the n-tier application, is there a difference between what you would consider your data access classes to be and your repositories?
I tend to think yes but I just wanted to see what other thought. My thinking is that the job of the repository is just to contain and execute the raw query itself, where as the data access class would create the context, execute the repository (passing in the context), handle mapping the data model to the domain model and return the result back up...
What do you guys think? Also do you see any of this changing in a Linq to XML scenario (assuming that you change the context for the relevant XDocument)?
Cheers Anthony