1,083 votes14 comments · [Closed] WCF Data Services Feature Suggestions · Flag idea as inappropriate… · Admin →
Good news: this is coming – and not just on entity types but on complex types as well. Enums are part of the OData v4 protocol. In fact, it was one of the things we argued vociferously for precisely because of the number of votes on this issue.
Its almost unbelievable that this isn't already implemented!
Good news: this is another thing that we felt was really important to take to the OData v4 protocol committee. This feature will be available in the near future as we finish work on our v4 stack.
Reopening since this was originally completed for EF6 but the feature is not available to Entity Framework Core.
I agree this is a must have!
Other required properties:
- Group name (to allow indexes over many properties; if it is empty, it applies to just the property where it is declared; if it is not empty, all properties with the same group name are added to the index definition.
This has some problems, however:
- The actual column name may be explicitly defined in configuration by code;
- The actual SQL to use for index creation depends on the current DB engine.
Hope the Entity Framework team can do something about these problems, this is quite necessary!
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.
Allow having properties that contain the result of formulas. The formula should be specified in a new attribute or fluently.