CODEWITHSUNDEEP
c#entity-framework-4
AlexCode
AlexCode

Reputation: 4123

EF4 Custom Entities within the same edmx

I have an edmx file that reflects 100% my DB schema. Along with this I need to create some custom Entities based on the existent, pretty much like a view that will aggregate fields of several entites into a single one.

The problem is that this isn't quite working. I tried several approaches but it always gave me conflicts with the actual entites already on the edmx.

I need to have those entities that reflect my DB schema, so do I have to create another edmx file to hold my custom entites and avoid colisions?

I also though of:

Could anyone point me to some examples?

Upvotes: 0

Views: 625

Answers (2)

Ladislav Mrnka
Ladislav Mrnka

Reputation: 364249

You can't define two entities based on same table except special cases (table splitting, hiearchy mapping). In this case you have to use DefiningQuery as @James suggested or QueryView. The difference is that DefiningQuery is defined in storage model and it is common SQL. QueryView is defined in conceptual model and it is ESQL defined on top of already existing entities. QueryView supports only some features of ESQL (for example it doesn't support aggregate functions). In both cases you have to modify EDMX directly (XML), these features are not supported in designer.

Database view mentioned by @James is also an option if you don't want to use these advanced EF features. You can as well simply expose predefined queries on your object context and map return projection to custom type.

Be aware that neither of these methods will allow you to modify, insert or delete data.

Upvotes: 1

James Gaunt
James Gaunt

Reputation: 14783

I think what you are describing is a view so this is probably the right way to go.

You can store the view code in the edmx using the DefiningQuery node. You don't need to create the view in the database. However there is no designer support for this feature, you will need to hand edit the edmx. The changes you make should be persisted if you refresh the edmx from the database using the designer.

Details here:

http://msdn.microsoft.com/en-us/library/cc982038.aspx

http://blogs.msdn.com/b/davidebb/archive/2010/10/01/the-easy-way-to-create-an-entity-framework-defining-query.aspx

It would be easier just to create the views in the database, and let the designer find and model them.

This entity will be read-only, but of course you can then assign SPs for UPDATE/INSERT/DELETE if you want to support modifications via this view.

Upvotes: 2

Related Questions