When an EDC Datasource has been added to the Vocabulary, its Entity properties for database interaction are displayed. Notice that several properties are conditionally modifiable based on other properties.

Note: The basic and document mapping Entity properties are discussed in Add and edit entity nodes and their properties
Table 1. Enterprise Data Connector (EDC) Entity Properties
Property Description Applicability Values and Defaults
Entity Identity Specifies which attributes (if any) act as its Entity's primary key. - Choose multiple attributes on the pulldown list by opening the list then holding the CTRL key while clicking the selections.
Datastore Persistent Indicates whether this entity will be database bound. Required. Yes, No, defaults to No.
Table Name Name of database table, chosen from a drop-down list of all database table names, fully-qualified with catalog and schema if applicable. Optional, only active when the entity is Datastore Persistent Value selected. When not specified, the system infers the best matching table from database metadata.
Datastore Caching Caching technique, chosen from a drop-down list. Indicates whether instances of this entity are subject to caching. Optional, only active when the entity is Datastore Persistent. Values are:
  • No Cache or blank (default) - Disable caching.
  • Read Only - Caches data that is never updated
  • Read/Write - Caches data that is sometimes updated while maintaining the semantics of "read committed" isolation level. If the database is set to "repeatable read," this concurrency strategy almost maintains the semantics. Repeatable read isolation is compromised in the case of concurrent writes.
  • Nonstrict Read/Write - Caches data that is sometimes updated without ever locking the cache. If concurrent access to an item is possible, this concurrency strategy makes no guarantee that the item returned from the cache is the latest version available in the database.
Identity Strategy Strategy to generate unique identity for this entity. Enabled when Entity Identity is not specified and DataStore Persistent is set to Yes Native, Table, Identity Sequence, UUID (These are described in the following table.)
Identity Column Name Name of the identity column, chosen from a drop-down list consisting of all column names associated with the table. Enabled when Entity Identity is unspecified. System attempts to create a match as entityName_ID.
Identity Sequence The fully-qualified name of the sequence to be used. Applicable when Entity Identity is unspecified and Identity Strategy is Sequence. System attempts to create a match as entityName_SEQUENCE.
Identity Table Name The fully-qualified name of the identity table to be used, chosen from a drop-down list of all table names and sequence names. Applicable when Entity Identity is unspecified and Identity Strategy is Table. When not specified, the value defaults to SEQUENCE_TABLE.
Identity Table Name Column Name The name of the column in the identity table that is used as the key (the name of the entity). Choose from a drop-down list of all columns in the table selected in the Table Name field. Applicable when Entity Identity is unspecified and Identity Strategy is Table. When not specified, the Name column name of the Identity Table defaults to SEQUENCE_NAME with data type (String).
Identity Table Value Column Name The name of the column that holds the identity value. Chosen from a drop-down list of all columns in the table selected in the Table Name field. Applicable when Entity Identity is unspecified and Identity Strategy is Table. When not specified, the Value column of the Identity Table defaults to NEXT_VAL with data type (Big Integer).
Version Strategy Strategy to control optimistic concurrency. Optional. Tells Hibernate how to handle table locking. See the Hibernate Developer's Guide for more information. Version Number, Timestamp
Version Column Name Name of the column that contains the version number or the timestamp. Applicable and required when Version Strategy is specified. The specified column name is created when you update the database schema.
Note: Identity and strategy concepts are general relational database concepts. Refer to your RDBMS brand's documentation for more information, especially the identity strategies that are specific to certain brands. Also see Identity strategies and Advantages of using Identity Strategy rather than Sequence Strategy .
Table 2. Description of the Identity Strategy values
Strategy Description
Native Allows database to choose best possible identity strategy.
Table Uses a database table, whose name is specified in Identity Table Name. This table will have two columns: a name column and a value column. (Previously referenced as "increment".)
Identity Uses the native identity capability in DB2, SQL Server (the column is defined as an "identity" column in the database schema).
Sequence Uses sequence capability in DB2, PostgreSQL and Oracle.
UUID Generates 128-bit UUID string of 32 hex digits. (Previously referenced as "uuid-hex".)
Note: Databases mentioned in the Identity Strategy table do not imply that they are currently supported RDBMS brands. For the current list of supported RDBMS brands, access the web location Corticon Supported Platforms Matrix .
Note: PostgreSQL limitation in EDC—Hibernate has a limitation when you attempt to perform write operations to a PostgreSQL view where a sequence is used for a column in the view. Hibernate is not updating its in-memory object, and always returns the same initial number, so the Database Sequence number is not incremented. Alternative approaches include modifying the view schema to not use a sequence on a column, developing a customer callout to perform the operation, or utilizing ADC.