Comments (1)
Hi @samiyariceboy,
There are many features that are not supported. We don't pretend to be an ORM, or support every single feature of various ORMs. The specifications are designed for simple queries, and usually for fetching entities/aggregates that you intend to modify.
If you have complex queries, you should have dedicated query objects and use the full potential of the ORM you're using. I know folks are using specs also for read operations, but I discourage that. There is no reason to fetch entities and utilize the domain model for read operations, instead, you should project directly to the result.
Btw, you can also use the specs directly (without repositories) while building your queries and projecting the results. Here is an example of how to combine all that. You apply your spec, continue building it (distinct doesn't make sense here, but just for the sake of demonstration), and projecting (in this case Automapper just as an example)
var spec = new CustomerSpec(1);
var result = await _dbContext.Customers
.WithSpecification(spec)
.Distinct()
.ProjectTo<CustomerDto>(_mapper.ConfigurationProvider)
.ToListAsync();
from specification.
Related Issues (20)
- Update LangVersion to C# 10 or 11
- Update conventions and styling
- Update Sample projects
- Remove obsolete API
- Update pipelines.
- Including nullable/optional navigation property causes only non-nullable connected objects to be returned HOT 3
- Unable to apply Take() to a navigation property HOT 5
- Refactor and improve integration test fixtures.
- Why do the Update and Delete not returning anything? HOT 3
- Logging in the Package HOT 4
- Feature Request: Deletion of entities via specification HOT 5
- Shadow properties HOT 4
- Query to return anonymous type HOT 4
- Question: Can I some how join table "B" when my entity T does not have a navigation property to "B" ? HOT 2
- Expression Evaluation HOT 8
- Simplify Cache usage HOT 5
- DbSet<T>.WithSpecification together with ISpecification<T, TDestination> throws SelectorNotFoundException HOT 4
- Conceptual question about the ORM specific implementations HOT 2
- Is it possible to use generic repository approach like this? HOT 1
- Specification - Include with Where clause HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from specification.