Give the developers more extensibility on the metadata creation.
Sometimes it is needed to change the metadata at run time on either the client or the server. It would be nice to be able to have a mix of automatic metadata creation (through EF) and manual manipulation. An example of this need could be for server side encrypted properties and the need to add a new property with the unencrypted value. Read this question on StackOverflow for more info: http://stackoverflow.com/questions/18118091/how-to-add-a-property-to-an-entitytype-after-it-has-been-added-to-the-data-store

-
Michael Lysaght commented
I have a need for this also, the same as Daniel, I need to add navigation properties between related entities that are described in different metadata stores. In my scenario I have DTOs that are described by custom metadata and a lot of lookup and supporting tables that are described in EF generated metadata.
http://stackoverflow.com/questions/22402366/combining-metadata-from-multiple-sources
-
Daniel commented
I'd really like to have this feature. I need to create some navigation properties between my entity framework entities and pocos.
-
Samuel Berthelot commented
definitely need that. I don't use EF and the metadata returned by OpenAccess are incomplete.
See : http://stackoverflow.com/questions/18617075/breezejs-adding-referential-constraint-to-an-entity-type
-
Brian Sayles commented
I would like this feature a lot. I have the need to add unmapped properties to the metadata so I can access them via knockout.
-
Ward Bell commented
I am a big fan of this suggestion.