Managing Master Data with webMethods OneData 10.5 | Managing Master Data with webMethods OneData | Implementing webMethods OneData | Managing Object Constraints | Constraints In Objects
Constraints In Objects
Foreign Key Constraint Caption Display
Passive Constraints
In OneData, you can maintain both database level constraints, such as primary key, foreign key, unique value constraints, and check constraints, and application level constraints called, passive constraints.
When an object is created in OneData by an import, such as from an external database, by running the SQL DDL script (Update Schema), or using the Synchronize Structure utility, the primary key, foreign key, and check constraints are recognized and automatically created within OneData. You can create additional constraints as needed.
Constraint Name
Primary Key
Column in an object that holds the value unique to a record. It defines the way the insert, update, and delete statements are generated and executed for a data object. Single or multi-part primary key can be defined for an object.
Foreign Key
Column in an object that holds the relationship to another object. It is mapped to the primary key column of the other object.
Unique Constraint
Column in an object that ensure uniqueness on non-primary key columns.
Check Constraint
Constraints that allow database level specification of a particular condition on each row in a table.
Note: OneData does not support check constraint on SQL Server.
Passive Constraint
Constraint used to:
*Validate the combination of entries being loaded or entered.
*Restrict the entry of data to valid combinations.

Copyright © 2011-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.