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.
-
Exclude function as opposed to Include
There should be to each Linq to Entities query an extension "Exclude" that returns IEnumerable<TSource> and the excluded fields will not be selected from the store/source.
12 votes -
Support concurrency checks in derived types when using TPT inheritance
Remove the limitation to perform concurrency checks on derived types. Now you may only use properties from the base type for concurrency checks.
12 votes -
More informatin from referential integrity constraint violation exception
I get so frustrated by the referential integrity constraint violation and the fact that the exception thrown contains no information about which fields are causing the problem.
Here's the full message for reference:
"A referential integrity constraint violation occurred: The property values that define the referential constraints are not consistent between principal and dependent objects in the relationship."Could you please update this exception to provide some key information so that we can track this issue down?
Thanks,
-Aaron12 votes -
11 votes
-
Allow ignoring issues with dropping non-existent foreign keys in Migrations
When converting an existing system to Code First Migrations sometimes the schema is in an inconsistent state. In SQL we can handle this by testing for exists and only dropping if it does. I handled this in code by catching the exception when trying to drop a foreign key that doesn't happen to exist in the database being migrated. this works when run as part of the upgrade, but doesn't work when running the Update-Database Powershell command. Below I have copied the code and error message for some context.
try
{
this.DropForeignKey("EDWAdmin.MetadataTableNote", "FK_MetadataTableNote_MetadataTable",);
}
catch
{
//swallow the exception if…11 votes -
Interchangeable Backing Database
I would like to write my code against the EF and have it work with SqlServer Express and SQlServer Compact (or even MySQL and Oracle). It would be great if I could swap these out at runtime, even, pointing to different databases as needed. This would require some improvements to SQLServer Compact, but also some improvements to EF.
11 votes -
Support SQL Server Schemas/Owners as CLR namespace/classes
SQL Server schemas (or owners) should reflect into CLR namspace branches or inner classes.
If you have Sales.Customer and Orders.Customer on the database, that shouldn't be Customer and Customer1.
11 votes -
Define RelatedProperty on an inherited foreign key
Allow mapping to entity in a derived class based on a property in base class.
Normally, we create a [RelatedTo] property for a foreign key defined in the same class.
But it would be quite handy to be able to define [RelatedTo] on a Foreign Key defined in the base class.
11 votes -
Merge EDMX designer with Class Designer
Visual Studio already contains Class Designer and UML Class Desinger. I don't need another so merge all them
10 votes -
10 votes
-
sql ce 4.0 local cache agent
Is there a possibility in the near future provide a SQL Server Compact 4.0 DB to synchronize with SQL Server, unfortunately, offers some of the SyncFramework for this version at no SyncCeProvider .... and the opportunity to work with a local cache async one is also forbidden, because it is supported only in version 3.5.
Unfortunately, I am clueless and if needed an alternative offered by the DB once support for the Entity Framework and the Local Cache Agent.
The version of SQL Compact 3.5 would work but unfortunately I have the problem that the auto-increment columns are not generated…
10 votes -
Code First better attributes
* Decimal Scale/Precision
[Column(DecimalScale=18, DecimalPrecision=2)]* Nullable indication (For string is essential):
[Column(NotNull = true)]* All in one:
[Column("TestName", NotNull = false, MaxLength = 250, MinLength = 3, Default = ""])
public String Name { get; set; }[Column(NotNull = true, MaxLength = 0, Default = 0])
public int Count { get; set; }10 votes -
9 votes
-
Custom Accessors (Getters/Setters) in CodeFirst
I should be able to put basic data validation on all of my public fields.
9 votes -
Support unsigned integer (e.g. uint) properties and keys
If my model contains an int ID it's automatically detected as a Key field.
I'd like to have the same support for uint ID and similar types.9 votes -
9 votes
-
Support all mapping inheritance strategies
Support all mapping inheritance strategies, well documented, as mentioned here: http://www.agiledata.org/essays/mappingObjects.html
9 votes -
Add polymorphic associations support
Add support for polymorphic associations like <any> and <many-to-any> in NHibernate.
9 votes -
Support for ASP.NET EntityDataSource and DynamicData for EF6
Because in EF6 the ObjectContext class is being moved into the EntityFramework assembly, existing code will treat it separately from the "old" ObjectContext in the System.Data.Entity assembly.
I use EF CodeFirst in a mixed MVC / WebForms(DynamicData) application.
Either bring out new versions of EntityDataSource and DynamicData for EF6 or provide a way from going from a EF4/5 ObjectContext to an EF6 one.
9 votes -
Clear, Complete, and Accurate Documentation
Break the mold! Provide clear concise documentation that describes the API, the intended use for each API, the purpose and use (with examples of the arguments to each method), and explanatory samples and snippets that are both complete and clearly show the intened information.
9 votes
- Don't see your idea?
