Overview

This article is relevant to entity models that utilize the deprecated Visual Studio integration of Telerik Data Access. The current documentation of the Data Access framework is available here.

When persisting objects, the objects require an "identity", so as to uniquely identify them for storage and retrieval. This in-memory id is normally mapped directly to a primary key column or columns in the database. Every object in Telerik Data Access has a unique identifier, i.e. a "primary key" from the database point of view. The identifier has to be defined when the object is made persistent (except when a key generator mechanism is used). Using this identifier, you can directly retrieve an object from the database.

This section provides examples of how to define identities in Fluent Mapping models:

• Single Field Identity
• Internal Identity
• Composite Field Identity
• Identity Per Configuration Level