Issue 1
Consider the following scenario:- You add an ADO.NET entity data model that is generated from a database in a Microsoft Visual Studio 2010 Service Pack 1 (SP1) project.
- You use Entity Designer to change the StoreGeneratedPattern attribute for an entity key property to Identity or Computed.
- You try to change data through the application.
In this scenario, an unexpected data entry or data corruption might occur in the corresponding database table column.
Note When this issue occurs, the conceptual schema definition language (CSDL) section of the .edmx file contains the new value for the attribute and the store schema definition language (SSDL) section contains the old value.
Issue 2
Consider the following scenario:- You have an ADO.NET project in Visual Studio 2010 SP1.
- A StoreGeneratedPattern attribute in the SSDL section of an .edmx file for the project differs from the StoreGeneratedPattern attribute in the CSDL section.
- You manually edit the attribute in the SSDL section to match the attribute in the CSDL section.
- You perform the Update Model from Database operation.
- You try to change data through the application.
Note When the Update Model from Database operation is performed, the value of the StoreGeneratedPattern attribute in the SSDL is overwritten.