Contents
Your Repository returns Domain Entities which map to tables and have methods which presumably use fast queries rather than exposing a IQueryable and leaving it to the user to discover which queries are slow.
What’s the difference between generic repository and unit of work?
The generic repository has operations that will be performed on the data layer for a particular model (table) The concrete implementation of the unit of work uses entity framework under the hood (DbContext) to save the changes to the database, and a new instance of the DbContext class is created per unit of work
Which is the typical design of a repository?
Our typical design is to have a context wrapped inside an Repository which is Dependency Injected into a UOW class. This way we can have a Unit Test that mocks the Repo returning fake DB results. A unit of work tackles this exact issue. It inverts the order of operations.
Why are UOW-less repositories not built in memory?
Uow-less repositories are built under the assumption that database interactions are limited to object-based get/set methods; and that any data stitching or operations (e.g. a group by + count) is done in memory. While that works on a technical level, it fails on a performance level.
How to use ” repoquery ” command to list package dependencies?
You can utilize the repoquery command in order to gather a list of packages that are dependencies of a package that you would like to update. Do note that this will grab the latest version of the dependencies even if you specify a version for the package that you are querying
How to implement a repository in database access project?
Then in database access project you can implement this repository in the most efficient way current database framework will allow. So, instead of mirroring database structure in your repository, have abstractions which fit domain needs and then implement those abstractions by effectively using database features.
Can a repository return more than one type?
Repositories are perfectly capable of returning more than one type, but it feels dirty to do so when the repository was created in essence to handle one given entity type. In my opinion, this is nothing more than developer error. You’ve implemented a system that works on a technical level, but has considerable performance issues.