Entity Framework Feature Suggestions
Welcome! You can use this site to tell the Entity Framework team what features you want to see in future versions.
Remember that this site is only for feature suggestions and ideas!
If you have technical questions or need help with EF try StackOverflow or visit our forums.
If you want to report a bug you found in EF use the Entity Framework project page on CodePlex.
If you want to find more information about the Entity Framework go to our MSDN site.
-
6 votes
-
EdmGen.exe should support generating an edmx file from a connection string
EdmGen.exe should support generating an edmx file from a connection string.
In .net 3.5, EdmGen2.exe (http://archive.msdn.microsoft.com/EdmGen2) was able to generate an edmx file from a connection string.
But for (EF) .net 4.0, we have lost this ability.
Thank you.
6 votes -
Update complex type returned by Stored Procedure
When using option 'Update model from databes' VS should update complex types returned by SP - now every SP have to be updated manually
6 votes -
Cross Model Navigation Properties
but, it's a total mission and I haven't had enough time to get it working. I'd like to add an association which bridges two models using the designer. Both models contain tables from the same database.
6 votes -
Extensible Cache
Extensible first and second level cache.
6 votes -
View Generated SQL
It'd be great if entity framework had an integrated tool such as the Profiler from Hibernating Rhinos (http://hibernatingrhinos.com/products/efprof).
I am aware that you can view the SQL generated for simple select statements by hovering over the DbSet member during debug but it would be nice to have a tool like this built into Visual Studio or that simply outputs the generated SQL to the debug console.
This should be configurable / able to be disabled.
5 votes -
support scalar -valued function
scalar function is used usually some custom function to retrieve some only one value.
eg.custom ID not Guid5 votes -
support for ordering in Include()
using the include() with a 1 to many relationship, the data are loaded in the list without any specific order, forcing often to reload directly specifying the sort order
5 votes -
Add the ability to persist TimeSpan values (and others) as strings
The immediate need is to be able to map between TimeSpan values on the CLR side and their equivalent string representations on the database side.
Currently TimeSpan can only be mapped to the SQL time datatype, which does not make much sense since the time SQL type is meant for storing time-of-day while TimeSpan is meant to represent an arbitrary amount of time. Mapping between the two limits the TimeSpan to a 24 hours interval, which rarely makes sense.
In our current DAL we do this by persisting TimeSpan values as strings, calling TimeSpan.ToString() on the way down and TimeSpan.Parse()…
5 votes -
Extensible Architecture
Give developers the power to customize and extend the Entity Framework!!!!
5 votes -
Caching
Please include caching in EF. I have used Jarek Kowalski’s provider but it didn't cope with Stored Procedures or
5 votes -
ability to LINQ datacontext in disconnected mode
Like datatable.Select(Filter) , we need to query what's already loaded in the datacontext using LINQ , something like a disconnected mode , this would be really gret feature , its so difficult to do right now
5 votes -
Interception Mechanism
Allow specifying an interceptor (Castle, LinFu, Sprint.NET, etc) for modifying materialized entities. This allows injecting interfaces such as INotifyPropertyChanged, IEditableObject, etc.
5 votes -
User Definable Attribute on Entities and Navigation Properties
Can we have the ability to add user defined meta data to entities and properties so that we can pick up on these using T4 Templates. One such example is in the DataMemberAttribute, this takes a priority in the constructor it would be nice to be able to add this as a metadata value on a property, we need this so that we can use entities both in WCF and RIA Services, at the moment we have hijacked the summary field for this purpose.
5 votes -
Improve Entity Framework to utilize Dependency Injection for entity materialization
I would like to see EF upgraded to allow a user-selectable Dependency Injection container to manage materialization of entities. This would allow finer grained control over how objects are materialized, as well as support interface based definitions for entities.
5 votes -
Add stored procs to data sources
Stored procedures can be included in an EDM. It would be most useful if a proc's result set were available for drag and drop from the Data Sources list such as tables currently are.
5 votes -
Stop DefiningQuery being overwritten by edmx designer
The defining query element in the edmx XML needs adding by hand, but when reusing the update model from database it is overwritten.
It was be very useful if the defining queries are not overwritten, as we primarily work in a database first way... so the team isn't familiar with the edmx xml... however we have specific features requiring DefiningQuery which could be overwritten often... it means that DefiningQuery couldn't be a long term solution for us as it'll cause to much pain to producitvity & gotcha bugs.
5 votes -
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 -
Allow Include() and Projections to Co-Exist
If you use a projection in the select part of a query, any eager loading of data through the use of Include() in the main query is ignored... as explained here http://social.msdn.microsoft.com/forums/en-US/adodotnetentityframework/thread/d700becd-fb4e-40cd-a334-9b129344edc9/
This is short sighted. I like Include() because I can dynamically append them to a query, the work around of putting the data to be "Included" in the projection does not allow for this dynamic extension oof the query.
If a developer has explicitly stated they wish to Include some related data they are doing it for a reason, so it should be respected.respected that they are doing…
5 votes -
Use names defined in linq query in generated sql
Currently if you have something like
select new { Year = c.DateEntered.Year }
the generated sql uses C1 for the column name. I would find it very useful if the used Year.
5 votes
- Don't see your idea?