Kbase P23322: Is it essential to set up foreign key relationships during t
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/11/2003 |
|
Status: Unverified
GOAL:
Is it essential to set up foreign key relationships during the design phase with PeerDirect?
FIX:
The set up of foreign keys in the Designer is not absolutely necessary for straightforward replication to be successful, however, make sure that you don't currently have and don't intend on using the following:
a) tables don't or will not have foreign key constraints, therefore the order of replication is not important( as opposed to Parent tables replicating before child tables, in this situation, the tables will replicate in the alphabetic order)
b) worksets (sub-setting of data around base tables) and transaction sets (single units of work) depend on foreign key relationships.
c) cascading deletes - to maintain referential integrity, once a delete happens to a parent, it will cascade to all children automatically.
The manual designation of foreign keys is not necessary in PRD since it has an
Auto-Import feature. When you identify a table for replication, the PRD will read the database's key constraints and display the foreign key relationships automatically.