Entity Framework eager loading/reference data
I’m struggling to get my head around how best to eager load entities, and how to assign relationships when creating new entities. I’m using EF5 POCO, by the way.
Should Repositories return IQueryable?
I have been seeing a lot of projects that have repositories that return instances of IQueryable
. This allows additional filters and sorting can be performed on the IQueryable
by other code, which translates to different SQL being generated. I am curious where this pattern came from and whether it is a good idea.
Should Repositories return IQueryable?
I have been seeing a lot of projects that have repositories that return instances of IQueryable
. This allows additional filters and sorting can be performed on the IQueryable
by other code, which translates to different SQL being generated. I am curious where this pattern came from and whether it is a good idea.
What is the equivalent of Entity Framework in the world of Oracle shops? [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. Within the world of developers/firms specializing in building/deploying […]
Mapping a legacy database to ORM using wrapper classes
I want to use an ORM with a legacy database, but I don’t want to expose some of the underlying data types. For example, some of the columns are nullable doubles or floats and I want my domain model to use non nullable decimals.
Is there a better way to model a many-to-many relationship on the same table with Entity Framework?
The context We’re building a web application using Entity Framework 5.0. One of the requirements is that it should be possible for the administrators to link related products so that when someone browses to a product we can render a list “You might also like these products:“. Since a product can be linked to many […]
Why should I use List over IEnumerable?
In my ASP.net MVC4 web application I use IEnumerables, trying to follow the mantra to program to the interface, not the implementation.
Why should I use List over IEnumerable?
In my ASP.net MVC4 web application I use IEnumerables, trying to follow the mantra to program to the interface, not the implementation.
How do I split out a service layer
I currently have four projects in my website’s solution:
Is Entity Framework only for Asp .NET / Asp. NET MVC? [closed]
Closed 11 years ago.