To maintain data integrity when reading and writing data, Entity Developer uses type mapping rules that can be further modified by the user. For more information on the procedures for editing, adding, removing and resetting the data type mapping rules, refer to the Creating and Editing Type Mapping Rules section of this help file.
Database-Specific Options
In Entity Developer there are options specific for different DBMSs. When working with an Oracle database, the user can select the Numeric Primary Key as Identity check box to identify the single numeric field in the primary key of a table as Identity. For a SQLite database, the user can select the Integer Primary Key As Identity check box to identify integer fields in the primary key of a table as Identity. For a MySQL or Firebird database, the user can select the Identifier Case Sensitive check box to indicate that identifier names of database objects should be processed as case-sensitive and quoted if they are not lowercase. |
Entity Framework Specifics
Changes in the type mapping rules impact not only the .NET type properties in the conceptual model, but also result in changing the rules for the definition of storage types for columns in the storage model; since in Entity Framework a .NET type of a property in the conceptual model is unambiguously matched to the types of columns in the storage model that correspond to it, validation will fail, if the .NET type of a property in the conceptual model does not correspond to the type of a column in the storage model. Due to this peculiarity of Entity Framework and also due to the fact that it contains no information on the server type of a column, retaining only its storage type, it is possible that the Wizard, while generating a DDL-script to create new objects in the database, will indicate types of columns that do not correspond to the native types of the columns, which were used to create this model within the Database-First approach. The reason for that is that the types of the columns being created for the table in the database are defined based on the storage types of the columns in the storage model. Entity Developer for Entity Framework supports third-party providers, but models created in Entity Developer with their help can differ from models created using the same providers but in ADO.NET Entity Data Model Designer. For details on how to eliminate these differences in point of type mapping rules, see Third-Party Providers Support.
|