Ignore create/change of model for a SQL View using Entity Framework

Question

If I create a SQL view and write a model to represent that view I will still want it to map up to be able to read data from the SQL view. The Add-Migration code will see this as a new table because entity framework (version 6) doesn't understand views.

Is there an attribute that I could assign that would prevent migration code from thinking its a new table it needs to create or something in the model builder?

possible duplicate of Mapping Database Views to EF 5.0 Code First w/Migrations — Colin
– Colin, Commented Feb 25, 2014 at 11:34
I don't think this is a duplicate, I know that I can use the up/down code to control the migration but I would like future instances of migration code to not evaluate certain models (because the represent already created views) by means of an attribute like the suggestion from @Mashton below. — Csharpfunbag
– Csharpfunbag, Commented Feb 26, 2014 at 14:21

user5168688 · Accepted Answer · 2015-07-29 09:24:49Z

2

add migration nomaly. and after migration rewrite to:

public override void Up()
{
    Sql("CREATE VIEW [viewname] AS SELECT {any select expression} ");
}

public override void Down()
{
    Sql("DROP VIEW [viewname]");
}

answered Jul 29, 2015 at 9:24

user5168688

212 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Community · Accepted Answer · 2017-05-23 10:29:27Z

1

From this SO answer:

Add-Migration IgnoreViewClasses –IgnoreChanges

(Works for EF 4.3.1+)

This creates an empty migration, ignoring any newly created classes from now on.

edited May 23, 2017 at 10:29

CommunityBot

11 silver badge

answered Jan 14, 2015 at 15:43

Dunc

19k6 gold badges92 silver badges111 bronze badges

Comments

Mashton · Accepted Answer · 2014-02-25 13:08:10Z

-1

You can use the [NotMapped] attribute to stop code-first classes being migrated into database creation.

answered Feb 25, 2014 at 13:08

Mashton

6,4752 gold badges27 silver badges35 bronze badges

1 Comment

Csharpfunbag Over a year ago

NotMapped would cause the property to not link to the column in the table it represents which is not the desired goal in this case.

Collectives™ on Stack Overflow

Ignore create/change of model for a SQL View using Entity Framework

3 Answers 3

Comments

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related