Updating Key Attributes

Maintaining Tables with Related Constraints › Impact of Changing Structure Definitions on Constraints › Updating Key Attributes

Updating Key Attributes

When you update KEY entity-occurrence attributes, changing the DATACOM-ID, DATACOM-NAME, MASTER-KEY, NATIVE-KEY, and UNIQUE attribute-values affect constraints. All other KEY attributes not listed in the following table can be changed.

Attribute	Type of Constraint	Effect on Constraint
DATACOM-ID	Check	Not applicable.
	Foreign	When you attempt to change this attribute-value, CA Datacom Datadictionary clears the value.
	Unique	Not applicable.
DATACOM- NAME	Check	Not applicable.
	Foreign	When you attempt to change this attribute-value, CA Datacom Datadictionary clears the value
	Unique	Constraints become invalid because CA Datacom/DB names of keys are stored in the object. The constraints are rebound by SQL the next time the table is accessed. The referencing constraints also become invalid and are rebound by SQL the next time the table is accessed.
MASTER-KEY	Check	Not applicable.
	.Foreign	When you attempt to change this attribute-value, CA Datacom Datadictionary sets the value to N.
	Unique	Not applicable.
NATIVE-KEY	Check	Not applicable.
	Foreign	When you attempt to change this attribute-value, CA Datacom Datadictionary sets the value to N.
	Unique	Not applicable.
UNIQUE	Check	Not applicable.
	Foreign	It is meaningless to update a Foreign Key. When you attempt to change this attribute-value, CA Datacom Datadictionary sets the value to N.
	Unique	Not allowed if a constraint exists on this key. CA Datacom Datadictionary generates a DSF return code CON when you attempt to change the value of this attribute from Y to N. Drop the constraint before you make this change.