how to tell Entity Framework to ignore database generates values for insert or update?

Question

I'm new to Entity Framework in C#.

I'm having one computational column in my table table1(example). I will calculate the computational column value based on the other columns value. I don't want Entity Framework to include the computational column while performing insert/update operations. How can I make the EF to avoid that particular column. But I want to set the value for that particular column manually.

I searched for the same but i couldn't able to get the answer for my question. Kindly help me and thanks in advance.

possible duplicate of : https://stackoverflow.com/questions/12661881/exclude-property-on-update-in-entity-framework — Skyuppercut, Feb 05 '18 at 10:32

TheGeneral · Accepted Answer · 2018-02-06T00:19:59.417

You can use the NotMapped Annotation

Code first convention dictates that every property that is of a supported data type is represented in the database. That property can be created dynamically and does not need to be stored. You can mark any properties that do not map to the database with the NotMapped annotation.

[NotMapped]
public string Something
{
    get
    {
        return _something;
    }
    set
    {
        _something = value
    }
}

Update : this is will not map to the dB, so is probably not what you are looking for

Just to make this a more complete the DatabaseGenerated Annotation, are the droids you are looking for

An important database features is the ability to have computed properties. If you're mapping your Code First classes to tables that contain computed columns, you don't want Entity Framework to try to update those columns. But you do want EF to return those values from the database after you've inserted or updated data. You can use the DatabaseGenerated annotation to flag those properties in your class along with the Computed enum. Other enums are None and Identity.

Which can be used with the DatabaseGeneratedOption

Computed : The database generates a value when a row is inserted or updated.

Identity : The database generates a value when a row is inserted.

None : The database does not generate values.

[DatabaseGenerated(DatabaseGenerationOption.Computed)]
public string Something { get; set; }

notmapped will not create that particular column in the database. But, I'm setting the computational column value from DB side. will it be affect? — Gopi P, Feb 05 '18 at 10:59
@gopip You won't be able to pass it back to the client though — TheGeneral, Feb 05 '18 at 11:01

tschmit007 · Answer 2 · 2018-02-05T11:31:38.957

1

As you calculate your column server side the correct way is to configure the field at the context level with:

HasComputedColumnSql for ef-core
DatabaseGeneratedAttibute for EF-6 (HasDatabaseGeneratedOption for the fluent api)

If you use NotMapped, you will not get the value from the database.

edited Feb 05 '18 at 11:31

answered Feb 05 '18 at 11:25

tschmit007

7,319
2
31
40

i see that using HasComputedColumnSql updates all rows whenever an update happens for a particular row in DB ? Is it correct behavior OR am I missing something ! – kuldeep Apr 12 '18 at 11:47

how to tell Entity Framework to ignore database generates values for insert or update?

2 Answers2