Table of Contents

Search

  1. Preface
  2. Introduction
  3. Configuring the Data Director Application
  4. Establishing a Root Node
  5. Defining the Business Entity Model
  6. Configuring Business Entity Properties
  7. Configuring Reference Entity Properties
  8. Transforming Business Entities and Views
  9. Managing Many-to-Many Relationships
  10. Configuring Search
  11. Configuring Workflow Tasks and Triggers
  12. Configuring Security and Data Filters for Business Entities
  13. Integrating Data as a Service
  14. Configuring External Calls
  15. Designing the Data Director User Interface
  16. Localizing Data Director
  17. Provisioning Tool Frequently Asked Questions

Constraints

Constraints

The MDM Hub uses foreign key constraints to maintain relationships between child objects and parent objects. When you create a node in the business entity model, you must specify the MDM Hub constraint that defines the relationship between the child node and the parent node.
A foreign key is a field in a relational table that matches the primary key column of another table. In a foreign key relationship, the child object has a foreign key column and the parent object has a primary key column. The MDM Hub uses the keys to associate a parent record with a child record. The foreign key column of the child record contains the value of the associate parent primary key.
The following image shows a Phone child object linked to a Person parent object by a foreign key relationship:
An image of a Phone child object table linked to a Person parent object table by a foreign key relationship:
The Person object has a primary key column called ROWID_OBJECT and the Phone object has a foreign key column called Person_ID. The primary key value of 3 links the record for Tom to the record for the phone number 555-3333.
The constraint attribute requires the following syntax:
<
child base object name
>(<
foreign key column name
>).<
parent base object name
>(<z
primary key column name
>)
The following code shows the constraint attribute for the example:
constraint="C_PHONE(PERSON_ID).C_PERSON(ROWID_OBJECT)"

0 COMMENTS

We’d like to hear from you!