[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. Replication at the EntityFramework SaveChanges level

    Implement Replication to other databases in SaveChanges.
    I've tried to do it, but I can't save autogenerated IDENTITY values in replicated db's.

    1 vote
    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 →
  2. Improve Database First Support

    Code First is no match for real life situations and also Proxies create lot of runtime problems.

    We use Dictionary<Type,object> to store Lambda Expressions that are designed to act as Filters for one type. Here is the problem, at runtime code first entity type is a dynamic type leading to following problems.

    1. Dynamic Type implementation is hidden.
    2. It does not support INotifyPropertyChanged
    3. It does not allow us to inspect/validate property with partial methods which we were able to do with Database First (EDMX) Model.
    4. CreateSourceQuery is hidden, sometimes we want to only execute Any or inspect…

    5 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. [DefaultValue(...)] is not handled by Code First migration

    In a column I can add [DefaultValue] attribute, but at the end it is ignored by the migration step. Confused. Please add support for this.

    10 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Events for Insert and Update

    Some sort of hook to allow for custom managed code to be run when inserts and updates happen. Usage Scenarios:
    1) allow for SignalR updates of data realtime.
    2) complex validation rules.
    3) awesome cache invalidation
    4) additional logging techniques

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Foreign Key Constraints on Views

    The "create/update modell from database" functions of the EF designer should support foreign key constraints on views.
    As a result of the foreign keys we get navigation properties on the views.

    (In Oracle database it is possible to create (disabled) foreign keys between views.)

    5 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Use ICustomTypeProvider to aid in a runtime customisable multi-tenant solution

    It is easy enough to add properties to a ICustomTypeProvider class but getting EF to recognise the added field would make producing a customisable multi-tenant solution a lot easier.

    1 vote
    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 →
  7. namespace complex types

    Place complex types generated by the database in their own namespaces. Right now, when a stored procedure is imported, a complex type is generated and placed in no particular namespace, so all of the complex types are floating about.

    Perhaps instead, use the namespace that's been given to the model.

    3 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Better support for modeling and regenerating existing database views

    The current database first support for views is not very good. I would like to see: readonly views where no key is assumed, updatable views where key can be selected, and at least an remembering of the actual create view syntax so that "generate database from view" will create a view and not a table. I often import a database view into my model and often do "generate database from model" to create a new empty database I can compare to production to make sure they are in sync. To do the latter, I have to delete all the sql…

    3 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 →
  9. Better integration with Mainframe datasets

    Better integration with Mainframe datasets: instead of screen scraping or CTG or even Host Integration Server, using a EF Provider to unlock the data in a main frame would be a huge benefit to .NET developers

    1 vote
    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 →
  10. Allow dependent Foreign Key properties to have a StoreGeneratedPattern of Computed

    Allowing dep. FK properties of the model to be generated by the database is useful for activity auditing (e.g. user logged into the DB gets their employee ID attached to the record by a trigger in insert/update).

    I understand the issues of having the DB generate the value (the value could violate the FK), but I put that on the same level as a DBA or other admin changing values that violate the FK (since the DBA or admin is likely doing the coding of the trigger itself).

    1 vote
    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 →
  11. Add FILEGROUP Support

    It should be possible to create tables, indices, etc. on different file groups in order to improve performance.

    7 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 →
  12. Logging of underlying stored procedure and actual SQL call

    In production environments, there is always a requirement to log the underlying SQL calls when a WCF/Web site calls database and executes store procedures or any other SQL statement. Right now, via Entity framework there is no way that we can retrieve the actual SP call so that it can be logged for trouble-shooting purposes.
    It would be great if the product team can create some handle to get this information!

    1 vote
    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 →
  13. Sort and autoformat xml inside .edmx files before saving via EF Designer

    Need the EF designer to generate nodes inside .edmx file in exactly the same order they are present in the database (currently a list of entity properties is saved in reverse order in mappings section, also when you update the model from the database schema the ordering is messed up). Also before saving .edmx file EF Designer should auto format the document. This would help significantly with branching, merging and resolving conflicts during merge operations of .edmx files.

    Steps to reproduce: (1) Generate EF data model based on an existing database (2) Add a couple of new columns, indexes, foreign…

    2 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 →
  14. Database VIEW creation support and specific mapping of entites to views.

    Currently, to get Code First to create a database with a VIEW, the CREATE VIEW sql statement must be hacked a couple of Context.Database.ExecuteSqlCommand's. One to drop the table that EF created for the entities you're mapping to it and another to create the view using the same name as the table EF assumes is still there.

    When mapping an entity to a view, you have to use modelBuilder.Entity<T>.ToTable and treat the view as a table. Entity Framework assumes the view is still a table and assumes it's read/write. A new method of .ToView might be added to tell EF…

    13 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Persist/Query Calculated Properties (read-only)

    This is a very useful feature that is supported in NHibernate. Given this property in the Order Entity:

    public decimal OrderTotal
    {
    get { return Items.Sum(o => o.Total); }
    }

    EF should persist this "read-only" property which can also be used in LINQ queries.

    var results = from order in DbSet<Order>
    where order.OrderTotal > 100
    select order;

    I believe a current work around is to include an empty protected setter but that has code smell all over it.

    2 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. EF ODBC Support

    I have seen NHibernate have the capability to connect ODBC data source. I could not do that in EF now. I want to connect Informix through EF with ODBC Driver. I did not want to use Informix data provider for this type of setup.

    2 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. Allow inserting new entities with predefined identity column values (INSERT_IDENTITY)

    Especially for migration projects it would be useful to allow entities to be saved with predefined identity values.

    Until now you have to use ADO.NET to do this.
    SET IDENTITY_INSERT TableName ON
    INSERT INTO TableName (IdColumn, Column1)
    VALUES (234, 'Value')

    I would like to tell the DbContext to use this feature when saving new entities.

    3 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 →
  18. Support for MERGE (UPSERT) statement

    I would like to see the T-SQL MERGE statement supported. For multi threading situations it really would be useful.

    14 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 →
  19. Updateable Views

    I would like to see update-able views. This is available in Telerik ORM, and I have found it very helpful in situations where I initially assumed a grid would only need to display read only data, but was months later asked to allow editing.

    There are other ways to do this of course, but they require recoding. This would make certain maintenance tasks easy.

    9 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. Migrations: Allow Multiple Migration SQL Generator per Provider

    One way to allow community to contribute to EF Migrations is allow us to create more `MigrationOperation`s.

    For example, people can then add things like full text index, etc., things that are not in the core EF Migrations and are just boring SQL statements that need to be combined together.

    Currently, to build a provider agnostic `MigrationOperation`, you need to write the SQL generated for the operation in a class derived from `MigrationSqlGenerator`. If you want to add `CreateFullTextCatalog` operation and support SQL Server for example, you inherit `SqlServerMigrationSqlGenerator`, add a `Generate` method for your operation, and ensure all other…

    5 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 →

[Closed] Entity Framework Core Feature Suggestions

Feedback and Knowledge Base