none
Entity Framework 5 Upgrade Issues with Upgrade Model from Database RRS feed

  • Question

  • I have been using EF 4 against a brownfield database since EF4 was released.  I manually updated some of the strings fields to non-nullable from (None) in the model designer which allowed me to hide some legacy problems without changing the underlying database.

    The problem I have is that in EF5, those manually updated Nullable properties are reset back to the database column's nullable status.  

    Is this intentional?  It seems like a defect to me since EF4+ supported this.  

    If is is supposed to work this way, why are we allowed to change the Nullable property from (None) to False?

    Any suggestions or comments would be great.

    Monday, December 10, 2012 5:31 PM

All replies