[Closed] Entity Framework Core Feature Suggestions

This web site is planned to be retired on July 31, 2019, and it is no longer being monitored by the EF team at Microsoft.

We have decided to unify our feedback process to focus on our existing issue trackers at GitHub.com. We are not planning to migrate the list of ideas posted here, because some of these ideas and votes were submitted a long time ago and therefore the number of votes likely does not accurately reflect the current priority for customers.

You are welcome to re-submit your favorite ideas to our issue trackers. We only request that you first search for existing issues and try to avoid creating duplicates.

Please visit the EF Core issue tracker or the EF6 issue tracker depending on what product you want to report bugs, make contributions, or submit ideas for.

Note that our team will only fix bugs, implement small improvements and accept community contributions on the EF6 codebase. Larger feature work and innovation will happen only on EF Core.

If you want to learn how to use our products, visit our documentation pages.

If you have technical questions or need help, consider asking in Stack Overflow using the EF Core or EF6 tags.

Note that roadmap questions, bug reports, feature requests or ideas are not appropriate for Stack Overflow. Visit Stack Overflow’s help center for guidance on appropriate usage.

Search for existing suggestions

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Second Level Cache

    Entity Framework currently support only first level cache (cache for entities). I would like to see a second level cahce implemented in the next version (queries cache).

    965 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow filtering for Include extension method

    There is no ablity to filter included objects in ObjectQuery<TSource>.Include method.
    Allow filter predicate in Include method in Entity Framework.
    I suppose this method of ObjectQuery<TSource> may have following signature:

    /// <summary>
    /// Includes related objects which meet to predicate
    /// </summary>
    /// <typeparam name="TRelation">Type of related object on another end of navigation property</typeparam>
    /// <param name="relationSelector">Expression that returns set of related objects</param>
    /// <param name="predicate">Predicate that has to be met</param>
    /// <returns>Query</returns>
    public System.Data.Objects.ObjectQuery<TSource> Include<TRelation>(Expression<Func<TSource, IEnumerable<TRelation>>> relationSelector, Expression<Func<TRelation, bool>> predicate);

    865 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Mapping single model to multiple databases

    Like to be able to build a domain model over data in multiple databases. With out having to manage database objects - linked servers, views etc.

    818 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    31 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Table-Valued Parameters support

    TVP support for stored procedures

    610 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    34 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. IndexAttribute

    Create a IndexAttribute for annotating entities with index hints for the Database.
    For Example

    [Index(Direction.Ascending)]
    string MyProptery{Get;set;}

    486 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Table-Valued Functions

    Allow table valued functions. This will enable many other scenarios such as full text search or advanced sql querying where LINQ does not support certain TSQL constructs. It can be used as a fallback or last resort whilst still allowing results to be further refined in LINQ.

    TVFs are extremely powerful when used in this way with LINQ. A view or scalar function is not applicable in all scenarios as you may need to either provide a parameter or return a set of rows rather than a scalar. TVFs support these scenarios.

    408 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. XML data type support

    EF full support of XML field

    369 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    26 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support interfaces as entity and complex types

    It's unfortunate not to be able to mark interfaces for EF mapping (code first). This will allow to really abstract the implementation. Allows a unique representation of the data in the context of RIA Services (if Ria Services allows also for interface 'mapping'). This won't be very hard to implement since EF is happy when it subclasses... For the benefits: imagine you have only interfaces to declare your model. On the server side, you use EF to get your interfaces 'filled' from DB. on the client side you get those same interfaces filled by RIA services... You can reuse any…

    323 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Lazy loading of non-navigation properties

    At time we may require to lazy load at column level. For e.g. if we have a LOB column which could be huge, we may not want to load that upfront when the table is lazy loaded. Agreed that we can workaroudn this problem, but a straight forward way would be good to have

    267 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Detect only properties that actually changed with change tracking POCO proxies

    I've noticed that in the proxied poco classes, an entity is marked as modified whenever a property is set, regardless of whether the value has actually changed. I think it would be nicer if only truly modified entities are flagged as modified.

    214 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    This is something we can consider in EF Core if at some point we implement change tracking proxies.

    From the EF6 perspective we don’t plan to change the current behavior. An important part of the motivation to create change tracking proxies is to avoid the cost of performing data comparisons.

  11. Stored procedure mapping in EF Core

    EF6 supports mapping CUD operation to stored procedures in both Code First and EDMX based development.

    EF Core does not have this functionality yet.

    207 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support for hierachical queries and HierarchyID

    One of the things that most simple business applications require is heirarchy. Whether it be a tree for data selection or a threaded comment set, Heirarchy is horrible to implement in EF and LINQ - I'd like to see methods that support it better.

    201 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Ability to specify query and table hints in SQL Server

    Table lock, update lock ( WITH(UPDLOCK) / FOR UPDATE ).
    LockMode something like NHibernate.

    Also should support controlling parameter sniffing

    http://stackoverflow.com/q/9890699/85196

    192 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    12 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Merge method: automatic synchronization of relationships on a disconnected entity

    A problem encountered when an entity is instantiated using non-ef infrastructure, e.g. ASP.NET MVC model binder mechanism. Such entity is pure poco class without proxy. Updates of relationship of the entity can be only synchronized using manual approach according to MSDN(and proven by experience)
    http://msdn.microsoft.com/en-us/library/ee373856.aspx "If you are working with disconnected objects you must manually manage the synchronization."
    Manual synchronization is really painful approach and really not a good ORM style solution.
    The problem even becomes critical for me in decision to migrate my application to nhibernate due to the fact that nhibernate can do such synchronization without problems http://www.codinginstinct.com/2009/11/nhibernate-feature-saveorupdatecopy.html

    171 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Simple Static Delete and Update Methods

    Allow for simple delete and update operations that do not require multiple round trips to the database. They could be static methods on each Entity. For example:
    Cars.Delete(int ID)
    or
    Cars.Delete(Guid ID)

    This would delete a car record with the associated ID if it exists. The code generation template should be smart enough to create the static methods using the correct data type.

    For updates you would pass in the ID and a set of named parameters for the fields that need to be updated:

    Car.Update(10, {Status="Sold", ModifiedDate=DateTime.Now}

    I think people are doing this now using functions or executing SQL

    153 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Flexible stored procedures support: allow mapping entities with complex types

    So far a stored procedure cannot be mapped to an entity with complex properties. Well it can be mapped, but the execution fails at runtime. It would be great if we could map stored procedure columns to entity properties.

    150 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Decouple entity creation in EF and support entities without default constructors and publically settable properties

    EF should decouple the implementation of the entity objects from the mapping functionalities. The EF team could provide the current entity creation as a default variant which can be attached to the mapper. The developer has the option to provide it's own data transfer object layer. Therefore we need to abstract the entities through interface usage an a generic naming schema (dot notation of an object model like Person.Name). So the EF would be much more flexible to use.

    Note by Diego Vega: I am merging this idea with a few other ideas that are approximately equivalent but extend in…

    137 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Flag idea as inappropriate…  ·  Admin →

    This feature is at least partially implemented in EF Core 2.1. There is no custom binding but many additional patterns are now supported by convention, including injecting the property values in the constructor, injecting instances of services also in the constructor and on properties.

    Direct mapping to fields was already supported in 1.1.

  18. Full Text Search

    Provide Full-Text Search capabilities similar to Lucene.Net-NHibernate

    130 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Offer eager loading strategies

    I supposed that eager loading currently supports only single fixed strategy and except some rare cases this strategy always joins all eager loaded data to one huge record set - at least that is what I saw so far.

    I described the impact of such eager loading on Stack Overflow: http://stackoverflow.com/q/5521749/413501

    It would be nice to have some control over the way how eager loading is executed with possibility to define if eager loaded data should be joined into single result set with the main data or if they should be executed in separate query.

    Something like:

    var data =…

    117 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add support for dynamically extended queries as per LinqKit

    LinqKit has shown that is possible to make the creation of queries much more dynamic, with them being composed at run time dependent on external conditions. nHibernate is good at this and LinqKit helps, but it would be nice to have an official solution.

    114 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 12 13

[Closed] Entity Framework Core Feature Suggestions

Feedback and Knowledge Base