information_schema.referential_constraints.update_rule

mysql

type: ENUM NOT NULL
5.7-8

mariadb

type: NULL
Note:
The Update Rule; one of CASCADE, SET NULL, SET DEFAULT, RESTRICT, NO ACTION.
© 2022 MariaDB
5.1-10.8
type: VARCHAR NOT NULL
Note:
The Update Rule; one of CASCADE, SET NULL, SET DEFAULT, RESTRICT, NO ACTION.
© 2022 MariaDB
10.2-10.7

tidb

postgres

type: CHARACTER_DATA NULL
Note:
Update rule of the foreign key constraint: CASCADE, SET NULL, SET DEFAULT, RESTRICT, or NO ACTION.
© 1996-2022 The PostgreSQL Global Development Group
10-15
type: CHARACTER_DATA
Note:
Update rule of the foreign key constraint: CASCADE, SET NULL, SET DEFAULT, RESTRICT, or NO ACTION.
© 1996-2022 The PostgreSQL Global Development Group
7.4-9.6

cockroachdb

type: unknown
Note:
Update rule of the foreign key constraint: CASCADE, SET NULL, SET DEFAULT, RESTRICT, or NO ACTION.
© 2022 CockroachDB
2-21.2

mssql

type: VARCHAR(11) NULL
Note:
Action taken when a Transact-SQL statement violates the referential integrity that is defined by this constraint. Returns one of the following: NO ACTIONCASCADESET NULLSET DEFAULT If NO ACTION is specified on ON UPDATE for this constraint, the update of the primary key that is referenced in the constraint will not be propagated to the foreign key. If such an update of a primary key will cause a referential integrity violation because at least one foreign key contains the same value, SQL Server will not make any change to the parent and referring tables. SQL Server also will raise an error. If CASCADE is specified on ON UPDATE for this constraint, any change to the primary key value is automatically propagated to the foreign key value.
© Microsoft 2022
azuresqldb-current-sql-server-ver15