# Predefined Constraints Predefined constraint classes are available for frequently occurring business rules. The business rules can be isolated to a single table or can be applied across multiple tables. For more information about using predefined constraints, please see the [**Constraint-Augmented Generation tutorial**](https://colab.research.google.com/drive/1WCMQujfVKL5giULZXOPPIBoMfzR9Zj68?usp=sharing). ## Single Table These constraints can be applied within an individual table of your dataset

Constraint	Description	Example
FixedCombinations	No shuffling is allowed other than what's already observed in the data	The `city` and `country` values cannot be shuffled to create new permutations.
FixedIncrements	All the numerical values are increments of a whole number	All values in `salary` must be divisible by 1000
Inequality	The value in one column must always be greater than the other	The `checkout_date` must always be after the `checkin_date`
OneHotEncoding	The original data columns represent a one hot encoding scheme	Exactly 1 of the following columns has a `1` in each row: `not_subscribed`, `basic_subscriber`, `premium`
Range	The value in one column is bounded by the values in other columns	The `parent_age` must be in between `child_age` and `grandparent_age`
❖ ChainedInequality	A chain of 2 or more columns in an inequality	`purchase_date` < `start_date` < `end_date` < `expiration_date` < `termination_date`
❖ FixedNullCombinations	No shuffling is around for the missing values, other than what's already observed in the data	The `city` and `country` columns must both either be null together or not at all.
❖ MixedScales	The value of one categorical column determines the scale of another numerical column.	If the value of `test_type` is `'blood_pressure'` then the value of `test_result` must be within a reasonable for this test only.
❖ SelfReferentialHierarchy	A column in the table refers to a different column in the same table.	The `Manager ID` column refers to the `Employee ID` column in the same table.

## Multi Table These constraints can be applied between multiple different tables of your dataset.

Constraint	Description	Example
❖ CarryOverColumns	The same columns are present in a parent table and a child table, and the values of those columns have to match up according to the connection.	The account `Type` in one table must match the corresponding account `Type` in another table.
❖ DenormalizedTable	A table that was created by denormalizing a parent and child table.	The `Transactions-Users` table was created by denormalizing the `Transactions` and `Users` table. (The user info is repeated for each transaction they've made.)
❖ ForeignToForeignKey	There are foreign keys in multiple tables but no primary key to attach them to.	The `Warehouse ID` column in multiple tables is referring to the same concept.
❖ ForeignToPrimaryKeySubset	There is a 1-to-many connection between tables, but only certain values are allowed to have connections.	Only accounts with `Type=Premium` are allowed to have children in another table.
❖ PolymorphicRelationship	The values inside a foreign key column can refer to different tables, depending on the context.	A transaction log's `Details` might sometimes reference a row in the `Credit Accounts` table and other times in the `Debit Accounts` table.
❖ PrimaryToPrimaryKeySubset	There is a 1-to-1 connection between the primary keys of two or more tables but only certain values are allowed to have connections.	Only users with `Is Minor=True` are allowed to have an entry in another table.
❖ ReferenceTable	A table acts as an unchangeable reference. You do not want to synthesize an new information in it.	The `City` table should act as a reference; you do not want to synthesize new cities.

{% hint style="info" %} ❖ **SDV Enterprise Bundle**. This feature is available as part of the **CAG Bundle**, an optional add-on to SDV Enterprise. For more information, please visit the [CAG Bundle](/sdv/explore/sdv-bundles/cag.md) page. {% endhint %} {% hint style="warning" %} **Can't find a constraint?** We've deprecated some constraints where the equivalent functionality could be achieved using other SDV features. We recommend using existing SDV features to handle the logic instead of adding a constraint. For more information, see [Deprecated Constraints](/sdv/concepts/constraint-augmented-generation-cag/predefined-constraints/deprecated-constraints.md). {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sdv.dev/sdv/concepts/constraint-augmented-generation-cag/predefined-constraints.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.