Section 1

Preview this deck

purpose of Cascading referential integrity constraint

Front

Star 0%
Star 0%
Star 0%
Star 0%
Star 0%

0.0

0 reviews

5
0
4
0
3
0
2
0
1
0

Active users

0

All-time users

0

Favorites

0

Last updated

7 years ago

Date created

Mar 1, 2020

Cards (9)

Section 1

(9 cards)

purpose of Cascading referential integrity constraint

Front

to prevent orphaned records

Back

Cascading referential integrity constraint Set Default

Front

All the values that make up the foreign key in the rows that are referenced are set to their default value.

Back

Four options when setting up Cascading referential integrity constraint:

Front

No action Set NULL Cascade Set Default

Back

Cascading referential integrity constraint Cascade

Front

If a delete statement affects one or more rows in a foreign key table, those rows will be deleted when the primary key record is deleted. If an update affects rows in the foreign key table those rows will be updated with the value from the primary key record.

Back

Cascading referential integrity constraint SET NULL

Front

If a delete statement affects rows in a foreign key table, those values will be set to NULL when the primary key record is deleted

Back

Cascading referential integrity constraint No Action

Front

If an update or delete affects rows in foreign key tables, the action will be denied and an error will occur.

Back

Check Constraints

Front

Used to limit the range of the values that can be entered for a column. Ex: the age of a person cannot be a negative number.

Back

Coalesce

Front

Returns the first NON NULL value.

Back

Default Costraint

Front

If a field isn't supplied with a value, instead of it being NULL it'll be the default constraint you set.

Back